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 Delivered
Workspace Instana
Categories Go
Created by Guest
Created on Sep 29, 2022

go-sensor: Stop losing traces during service startup

When services start up, it takes a while until the instana sensor is ready to handle traces and transmit them successfully. Currently, all traces for calls during that timeframe are lost (e.g. fetching configurations, roles, etc. from supporting microservices). This renders service owners completely blind to these early calls.

A possible solution is to queue these calls, as long as the sensor is not yet ready.

In a colleague of mine already prepared a Pull Request with a patch proposal. It's a non-breaking change.

Alternative solution: Allow people to implement their own recorder by exporting the necessary structs in the go-sensor lib. This would be the much more complex solution -- especially for the customer.

Idea priority High
  • Guest
    Dec 14, 2022

    This feature is released and included in v1.47.0

  • Guest
    Oct 19, 2022

    That's not what your team said. They had those concerns, but it seems, that they could easily be adressed.

    Our proposal just involves the in-memory buffering of traces in a queue, which does not expose anything incl. no sensitive data. The filtering and sending stay separate. The same policies can still be applied. The data is not recorded as such, i.e. not persisted. Hence, there is no substantial decrease in security.

  • Guest
    Oct 18, 2022

    Thanks for reaching out. As our team in the PR replied, we are not able do this due to the security issue of recording sensitive data before receiving configuration.