Audit domain · 1 check

Business events are the part of the platform most often bought before it is used. A provider is configured during a proof of concept, a dashboard is built on it, and then the field names change on the producing side and nothing complains — the events keep arriving and the dashboard keeps rendering, on a field that is now always empty.

The single check in this domain establishes what is actually arriving: providers, volumes and event structure. It is a small answer, but it is the one that tells you whether the business dashboards in front of an executive are reading live data or a shape that quietly stopped matching.

Only one check — is that worth reporting?

Do you read the contents of our business events?

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