Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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 Delivered
Workspace Instana
Categories Other Tracers
Created by Guest
Created on Sep 14, 2023

OpenTelemetry Infrastructure correlation improvement

The customer is using the standard Otel protocol exporter (via http/grpc) and sends data to the instana agent on the host. https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol

They can see the calls in the Instana UI but the problem is Infrastructure correlation. Here is on call example:
https://instana.io/s/pmcWVzTAQaSUClmbihifew

As you may see we mapped the call to the host and looking into the Endpoint it looks fine:
https://instana.io/s/X-DHLNajRI6SNfo1crvmfw

But this information is somehow not visible in the Service view:
https://instana.io/s/-dbOjpQxQ3Oe53JmpmW8Vg

Idea priority Medium
  • Guest
    Reply
    |
    Nov 23, 2023

    There are 2 ways of OpenTelemetry Instrumentation for GoLang Apps.

  • Guest
    Reply
    |
    Nov 20, 2023

    Instana supports linking between spans/calls and entities based on OTel resource attributes.

    For OTel javascript auto-instrumentation, user needs to have an Instrumentation.js having resource detectors to support enough resource attributes. For example containerDetector is very key for the linking.
    Here is an example of Instrumentation.js in OTel official demo:

    /app $ cat Instrumentation.js
    // Copyright The OpenTelemetry Authors
    // SPDX-License-Identifier: Apache-2.0

    const opentelemetry = require('@opentelemetry/sdk-node');
    const { getNodeAutoInstrumentations } = require('@opentelemetry/auto-instrumentations-node');
    const { OTLPTraceExporter } = require('@opentelemetry/exporter-trace-otlp-grpc');
    const { OTLPMetricExporter } = require('@opentelemetry/exporter-metrics-otlp-grpc');
    const { PeriodicExportingMetricReader } = require('@opentelemetry/sdk-metrics');
    const { alibabaCloudEcsDetector } = require('@opentelemetry/resource-detector-alibaba-cloud');
    const { awsEc2Detector, awsEksDetector } = require('@opentelemetry/resource-detector-aws');
    const { containerDetector } = require('@opentelemetry/resource-detector-container');
    const { gcpDetector } = require('@opentelemetry/resource-detector-gcp');
    const { envDetector, hostDetector, osDetector, processDetector } = require('@opentelemetry/resources');

    const sdk = new opentelemetry.NodeSDK({
    traceExporter: new OTLPTraceExporter(),
    instrumentations: [getNodeAutoInstrumentations()],
    metricReader: new PeriodicExportingMetricReader({
    exporter: new OTLPMetricExporter(),
    }),
    resourceDetectors: [
    containerDetector,
    envDetector,
    hostDetector,
    osDetector,
    processDetector,
    alibabaCloudEcsDetector,
    awsEksDetector,
    awsEc2Detector,
    gcpDetector,
    ],
    });

    sdk.start();

    For more resource detector related information, please refer to https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/detectors/node

    1 reply
  • Guest
    Reply
    |
    Nov 15, 2023

    This functionality was delivered via an update to the OpenTelemetry Sensor, v1.0.16

    1 reply
  • Guest
    Reply
    |
    Nov 14, 2023

    The problem in this ticket was found on Jul 16-17.
    It is fixed now for this kind of scenarios. The service can be mapped to the infrastructure - host. In this particular scenario, not only mapping to the host, but also to the container, pod, and node.

    1 reply
  • Guest
    Reply
    |
    Nov 13, 2023

    We are looking into this to determine why the entity correlation is working on the host dashboard but not within infrastructure perspectives