This is an IBM Automation portal for Cloud Management and AIOps 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Filter on exit endpoints (Capture http headers for exit calls)
We are facing an issue due to restrictions in Instana.
We can't get contextual informations on endpoints going to non instrumented applications. The consequence is that we can't manage incidents the same way if they come from an internal or external source.
For instance, we evaluate an incident criticity based on the calculation of the number of users that have faced a specific error. We can do this on instrumented servers thanks to custom headers which pass a userid, but we can't calculate this on incidents involving external partners in spite of sending the same headers to theses partners.
We see two solutions that could hypothetically overcome this issue : - Be able to track custom headers on exit requests - Be able to filter on datas from sources that are instrumented. (for example the correlation with meta from front-end , or custom headers from entries to our back-end application)
Do you think any of those two solutions could be done ? Or maybe another that we haven't thought of?
Do not place IBM confidential, company confidential, or personal information into any field.