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 App Connect
Created by Guest
Created on Jun 12, 2026

RELATED IDEAS

Make it possible to create monitor events based on nodetype and not on nodelabel

At this moment a monitor event is emitted when the eventSourceAddress is equal to the nodelabel.terminal.terminalname. This makes that when you change the nodelabel of a node (to make it more readable what is does) you need to create an extra monitor model entry for this node with most of the time the same values as other nodes of the same type. So when you have 2 file Input nodes in 1 flow each of the input nodes needs to have an entry in the monitor model however you want to log the same data.
It would be easier if you could create monitor model profiles based on the type of node or on a combination of type of node and nodelabel so if needed you can log for specific nodes extra information.

This would also allow to use 1 logging application for all you integration flows using a limited amount of monitor model profiles which you can easily reuse on all your integration flows so you are certain all necessary data is logged.

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.