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

Dynatrace synthetic monitoring audit: monitors that pass, fail, or never run

Three checks on synthetic coverage — monitors that have not executed, monitors failing continuously without alerting anyone, and locations that no longer exist.
Book a free audit All 71 checks

What these checks read

Execution history

When each monitor last ran, and which have not run inside the window at all.

Persistent failures

Monitors failing continuously, and whether their failures reach an alerting profile.

Locations and credentials

Private locations that are offline, and monitors depending on credentials that have expired.

Why it matters

A synthetic monitor is a promise that somebody is checking the front door every few minutes. Three of the ways that promise quietly breaks are visible from the tenant: the monitor was disabled during a maintenance freeze, the private location it runs from was decommissioned, or it has been failing so long that the failure became the baseline.
The last one is the most dangerous, because the monitor is green on the "is it configured" question and red on the only question that matters. The check distinguishes a monitor that fails from a monitor that fails and reaches nobody, which is the pair that matters for incident readiness.
The output is a list with last-execution timestamps, not a coverage score. A score would let you feel better without changing anything.

Questions we get about this domain

Do you run our synthetic monitors as part of the audit?

No. The audit reads execution history and configuration. It never triggers a monitor, which would both distort your own data and count against your quota.

What about monitors in private locations we manage ourselves?

They are read the same way, and the audit additionally reports private locations that have stopped reporting — the usual reason a set of monitors silently stops running after an infrastructure change.

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