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 Functionality already exists
Workspace Instana
Categories Kubernetes
Created by Guest
Created on Dec 11, 2023

Limit what files are copied per pod by instana-instrumentation-init

The typical duration of instana-instrumentation-init is 2 seconds. This becomes an issue during node consolidation and when pods are moved to a new node.


I’ve analysed the reason for this slow performance, and it is likely due to the init container copying 12 139 files of 270 MB.


My specific pod is using .NET Core, which only needs 8 files of 3MB.


Currently the webhook uses a global flag to enable the copy of a SDK, i.e.

https://github.com/instana/instana-autotrace-webhook/blob/main/incubator/instana-autotrace-webhook/values.yaml#L74


Improvement Suggestion: To improve the performance of the init container, please use a K8s label to indicate for which SDK the container is opting-in. Like the current tracing opt-in label:

https://www.ibm.com/docs/en/instana-observability/current?topic=technologies-instana-autotrace-webhook#opt-in-or-opt-out

Idea priority Medium
  • Admin
    Henning Treu
    Reply
    |
    Mar 13, 2024

    Hi,


    this is already possible, either setting it globaly for everything the AutoTrace Webhook instruments, or Deployment specific:


    This is going to be added to the official documentation as we speak. I hope this resolves the issue for you already!


    Best regards

    Henning Treu - Instana Product Manager