Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Submitted
Workspace IBM Event Automation
Categories Event Endpoint Management
Created by Guest
Created on Dec 16, 2025

RELATED IDEAS

Extend EGW to support access logging with a customizable set of actions to be logged (e.g. logins, failed logins, subscriptions, event retrievals, ...)

Right now there are OTel metrics in the gateway that give us some information about clients that tried connecting and that connected. The consumption of messages already depends on whether they commit or not. Anyhow, all metric values are aggregations and normally for a limited amount of time. When we want to log every connection try and every login, we can enable audit logging but this is flooding the log system as it logs at least 1 (if not more) log entries for every event read by any consumer. As we have ~200K events per day and want to support 50+ consumers, this is not usable. We could achieve our requirements by enabling ingress tracing for the EGW but that was not recommended as a productive solution. We would like to have a kind of access protocol, that logs each login, connection termination, failed login, anonsymous login and configurable also each offset commit and maybe any event read action (but not every event but rather every n minutes or by batches). The detail logs should be configurable to turn them off without loosing the more important connect/disconnect actions.

We need this as proof for system interactions and to detect intruders / failed connection tries.   

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.