Audit domain · 1 check

Dashboards are the most visible artefact in the tenant and the least maintained. They are created per incident, per project and per executive request, they outlive all three, and nobody deletes one in case someone is using it.

This check produces the inventory with owners and modification dates. It does not score dashboard quality — that is a matter of taste and of who is reading. What it gives you is the basis for a decision you cannot make without a list: which dashboards are current, which belong to teams that no longer exist, and how much of your tile estate queries data that is no longer ingested.

Can you tell which dashboards are actually viewed?

Does the audit delete anything?

Nineteen domains, 79 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

An audit takes one run. The findings take one meeting. What you do with them is up to you.

Certified Dynatrace experts

How can we help? Send

Obzervability

Privacy Terms of use Accessibility