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 Not under consideration
Workspace DataPower Gateway
Created by Guest
Created on Mar 24, 2017

RELATED IDEAS

Increase number of events per second on Log Targets using syslog target type

Currently, using the syslog target type for a Log Target has a hard limit of 1000 events per second. This may seem like a lot but we had an IBM developer that was contracted kick out 120+ events per transaction for troubleshooting purposes. This is an extreme case but I can see a time in error situations where we could exceed this limit. There are creative ways to handle this such as creating multiple log targets each suppressing different types of events with the aggregate of all log targets essentially giving us what we would expect from one log target but that seems a cumbersome solution.

Idea priority Medium
RFE ID 102831
RFE URL
RFE Product IBM DataPower Gateways
  • Guest
    Jul 7, 2026

    I am adding this comment to strongly support this Idea. We are currently experiencing significant limitations with the syslog target type, specifically when our devices exceed 1,000 transactions per second (TPS).

    At present, log targets configured to capture only transaction response codes are dropping events under high loads (>1,000 TPS). This data loss directly impacts our monitoring and observability reports, resulting in incorrect transaction counts. Furthermore, we are losing critical latency log events on our physical appliances when traffic exceeds this 1,000 TPS threshold, even when the log target is dedicated solely to pumping latency logs.

    Because these dropped events undermine the accuracy and reliability of our enterprise observability stack, we urgently need the ability to increase the number of events per second supported on syslog log targets. Kindly consider prioritizing and implementing this RFE as soon as possible.

    Reply

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.