obs-dynatrace-support

To send OpenTelemetry traces to Dynatrace, configure the otlphttp exporter in your OpenTelemetry Collector, validate endpoint connectivity, and ensure correct token scopes for secure OTLP ingestion.

Dynatrace OneAgent telemetry issues in Kubernetes often stem from Operator misalignment or pod health failures; inspect operator resources, verify pod logs, and validate environment-specific authentication to resolve reporting gaps.

Ingesting metrics and logs into Dynatrace requires least-privilege token scopes configured for each specific signal type, ensuring secure and authenticated access for metrics, logs, and events data.

Migrating OpenTelemetry data to Dynatrace while minimizing vendor lock-in involves using OTLP endpoints and documenting which signals originate from OneAgent versus OpenTelemetry instrumentation.

Yes, you can use the Dynatrace Operator alongside OpenTelemetry collectors; this Skill guides environment-aware practices to distinguish OneAgent-assisted OTel data from standard Operator ingestion paths.

Validate Dynatrace OTLP endpoint connectivity by testing collector configurations in non-production environments first, confirming endpoint reachability, token scope validation, and ingestion path stability before production rollout.