Skip to Main Content
Cloud Management and AIOps

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 (

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 Not under consideration
Workspace Instana
Categories Tracing
Created by Guest
Created on May 27, 2022

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?

Kind regards,


Idea priority High
  • Guest
    Jul 1, 2022

    Thank you for reaching out.

    Based on the usecase , I will assume you are talking about HTTP reponse headers for exits, pleaase correct me if I get it wrong.

    For collecting HTTP response headers on exit requests, right now we only support it in Node.js.

    Could you tell me which libraries in which language/platforms you want us to expand our support for response headers capture on HTTP exits?