Audit domain · 1 check

Davis is the reason a platform costs what it costs: the difference between an alert stream and a root cause. So the attribution rate is a reasonable proxy for whether the platform is doing the job it is priced for.

When the rate is low, the cause is almost never Davis. It is upstream: entity continuity broken by a detection rule, a service that exists as 400 versions, or coverage gaps that leave the dependency graph incomplete. The check reports the rate and the cluster of unattributed problems so the conversation can start at the real cause — which usually lives in the Topology or Coverage domain.

What is a good attribution rate?

Does the audit change how Davis works?

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

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

Certified Dynatrace experts

Send

Obzervability

Privacy Terms of use Accessibility