Obervability
Services AudiTrace Resources▾ Contact
Book a free audit
Audit domain · 1 check

Dynatrace SLO audit: definitions that break on re-detection

One check on service-level objectives — whether each SLO’s entity selector still matches the entities it was written for.
Book a free audit All 71 checks

What these checks read

SLO definition validity

Every SLO, its entity selector, and whether that selector currently resolves to the entities intended.

Why it matters

An SLO is written against a selector, and selectors are written against entities that re-detection can replace. When a service is re-detected — after a deployment change, a naming-rule edit or a platform migration — the SLO does not error. It quietly measures a smaller set, or an empty one, and reports a perfect error budget.
The check resolves every SLO selector and reports the ones matching nothing or matching a set that has changed size sharply. An SLO reporting 100% because it measures nothing is worse than no SLO at all: somebody is making release decisions on it.

Questions we get about this domain

Why would an SLO stop matching its service?

Because the entity identity changed. Re-detection creates a new entity id for what a human would call the same service, and the selector — especially an id-based one — keeps pointing at the old one.

Should selectors be tag-based instead?

Usually, yes, and the Tagging domain is where the audit checks whether the tagging convention is consistent enough to support it. That ordering matters: tag-based selectors on inconsistent tags fail in a harder-to-see way.

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