Obervability
Services AudiTrace Resources▾ Contact
Book a free audit
Audit domain · 2 checks

Dynatrace OpenTelemetry audit: OTel sources and dual instrumentation

Two checks on OTel ingest — which sources are sending, and where OneAgent and OpenTelemetry are instrumenting the same workload twice.
Book a free audit All 71 checks

What these checks read

OTel source inventory

Which services and hosts send OpenTelemetry data, through which collector, and at what volume.

Dual instrumentation

Workloads reporting through both OneAgent and OTel, producing two entities and two streams for one thing.

Why it matters

Most estates arrive at OpenTelemetry sideways: one team adopts it, a collector goes in, and for a while both paths run because turning either off feels risky. That interim state is stable enough to survive for years and expensive enough to be worth naming.
The dual-instrumentation check is the useful half of this domain. It lists the workloads reporting through both paths, which is simultaneously a cost item (two streams, two entity sets), a data-quality item (traces that do not join), and a decision nobody has been asked to make.
The second check simply establishes the inventory: what is actually sending OTel today, versus what the architecture diagram says. Those are rarely the same document.

Questions we get about this domain

Does Dynatrace ingesting OTel change what the audit can see?

It changes where the data comes from, not the method. The checks read the tenant’s view of OTel sources and entities through the API, the same as every other domain.

Which path should we keep?

That is an architecture decision with real trade-offs and the audit does not pretend to make it. What it gives you is the list of workloads where the question is currently unanswered and being paid for twice.

The other audit domains

Nineteen domains, 71 checks, one read-only run. Each domain is a page.
FinOps Where the money goes, and what is recoverable Kubernetes Cluster coverage, versions, recurring failures Alerting Whether an incident would actually reach a human Audit log Who changed what, when, and outside business hours Coverage What is monitored, what only looks monitored RUM Real-user monitoring reach and privacy settings Grail Buckets, retention, annualized storage cost Pipelines Ingest processing, masking, drop rules Synthetic Synthetic monitors that pass, fail, or never run Topology Entity detection quality and entity explosion OpenTelemetry OTel sources and dual instrumentation Security Token scopes, expiry, dormant credentials Workflows Automation that fails or never fires Bizevents Business event provider hygiene Dashboards Dashboard inventory Davis Root-cause attribution rate OpenPipeline Route and pipeline resolution SLO SLO definitions that break on re-detection Tagging Environment tagging convention

See what this domain finds on your own tenant.

One read-only run covers all nineteen domains. You keep the report either way.
Book a free audit See how AudiTrace works

Find out what your Obervability is actually doing.

An audit takes one run. The findings take one meeting. What you do with them is up to you.
Certified Dynatrace experts
+1
Send
Obervability
Dynatrace implementation, managed services and support. Every finding comes with the source behind it.
Services
Services AudiTrace Case study
Guides
Dynatrace audit Dynatrace cost optimization Audit case study Articles
Reach us
© 2026 Obervability · All rights reserved.
Privacy Terms of use Accessibility