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 (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.

Status Under review
Workspace Instana
Categories Tracing
Created by Guest
Created on Apr 17, 2024

Add notes in application logs after instrumentation on how to disable auto-instrumentation for the application

When we instrument the containerised application, and some errors prevent it from starting, customers complain that instrumentation breaks the application. Some of them uninstall autotrace-webhook, some disable Autotrace Webhook, some add a namespace into the exclude list and reinstall autotrace webhook.

If we provide short instruction in application log on how to set label instana-autotrace=‘false’ it would save a lot of time for customer and give sense of simplicity.

Those issues are mostly the same. Would also be good to put link in application log to our public documentation with the topic and troubleshooting cases.


Clarifications provided by Oleg:


What I ment is to add instruction into application log.

When customer instruments applicatio and sees that his pod is restarting (or at least doesn’t see the result of autoinstrumentation) fist thing he checks is the log of the failing pod.

It is their Application log:

Something like:

==================

label

13:14:17.689 INFO |- DefaultPodSpecTransformation: Configuration is use libinstana init

13:14:17.689 INFO |- DefaultPodSpecTransformation: Configuration is use autotrace nodejs

13:14:17.696 INFO |- [AdmissionReview 81128a51-4ca6-4bf5-9d9b-676a6f37540b] Applied transformation DefaultDeploymentTransformation to the Deployment 'testapp/instana-tests'

yarn run v1.22.19

$ cross-env NODE_ENV=production node dist/main

{"name":"@instana/collector","thread":0,"__in":1,"hostname":"testapp-7f66746b94-jnvjc","pid":28,"module":"pidStore","level":30,"msg":"Starting with pid 28","time":"2024-03-21T13:18:48.799Z","v":0}

. . .

==================

And sees there some error that causes the pod to restart.

What is first thing he would do if he can’t fix the app? – disable Instrumentation, and usually customers do not read documentation. They read their application logs!

So why not to put there information for them like:

==================

label

13:14:17.689 INFO |- DefaultPodSpecTransformation: Configuration is use libinstana init

13:14:17.689 INFO |- DefaultPodSpecTransformation: Configuration is use autotrace nodejs

13:14:17.696 INFO |- [AdmissionReview 81128a51-4ca6-4bf5-9d9b-676a6f37540b] Applied transformation DefaultDeploymentTransformation to the Deployment 'testapp/instana-tests'

INSTANA TRACER NOTE: If you would like to disable auto instrumentation of the application set label: instana-autotrace=”false”

In the deployment/statefulset/pod.

More info: https://www.ibm.com/docs/en/instana-observability/current?topic=kubernetes-instana-autotrace-webhook#ignoring-resources

yarn run v1.22.19

$ cross-env NODE_ENV=production node dist/main

{"name":"@instana/collector","thread":0,"__in":1,"hostname":"testapp-7f66746b94-jnvjc","pid":28,"module":"pidStore","level":30,"msg":"Starting with pid 28","time":"2024-03-21T13:18:48.799Z","v":0}

. . .

==================





Idea priority Medium