Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Feb 26, 2020

Need a 'NOT' flag or blacklist for objects in the Object Filters tab of log targets

We have a particular service that is going through the Datapower. It generates a huge volume of transactions... millions in a 24 hour period as opposed to all other services which tend to generate tens of thousands in the same 24 hour period. We know this only due to our use of the DataPower Operations Dashboard (DPOD). It looks like the high volume of transactions is causing problems with the Datapower syslog facility because syslogs are being dropped to the DPOD and we keep getting messages within DPOD about that. Due to the huge volume, we need to separate out the logging for this single service from the same for all other services. We can create a new log target and configure it to only accept logs from the problematic service. However, we don't have an easy way to exclude the logs from the same problematic service from appearing in all of the other log targets with subscriptions to the same category UNLESS we add an object filter to them that represents all of the other objects that should be logged to that target. Doing that will be quite cumbersome and require a modification to the log target every time that we add a new service too. We need a way to an object or set of objects from a log target as opposed to having to specify all of them for inclusion.

Idea priority Medium
RFE ID 140574
RFE Product IBM DataPower Gateways