OpenTelemetry Infrastructure correlation improvement

There are 2 ways of OpenTelemetry Instrumentation for GoLang Apps.

• Manual instrumentation. We can see the example used in OTel official demos. Instana can support entities/spans linking very well in container environments. Here are examples:

• https://opentelemetry.io/docs/demo/services/checkout/

• https://opentelemetry.io/docs/demo/services/product-catalog/

• Automatic instrumentation (in beta stage). You can refer to examples in "https://github.com/open-telemetry/opentelemetry-go-instrumentation". User needs to set a sidecar for a container environment. Right now Instana only support linking to logical service. While this beta project is continuously being improved.

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

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

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.

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