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

Dynatrace tagging audit: convention, consistency and chargeback

One check on tags — whether environment, ownership and cost-allocation tags follow the convention you defined, and which entities carry none.
Book a free audit All 71 checks

What these checks read

Tag convention compliance

Entities against your own tagging convention: which keys exist, which are missing, and where values are inconsistent.

Why it matters

Tagging is infrastructure for everything else in the tenant. Management zones, alerting profiles, SLO selectors and every chargeback report are all downstream of it, which is why an inconsistent tag estate produces failures that look like problems in five other domains.
On the tenant in our case study, 384 hosts carried no cost-allocation tag, which made chargeback arithmetically impossible — not hard, impossible. There is no report that can attribute consumption to a team when the attribute does not exist.
The check compares the estate against your convention rather than against a convention of ours. If you do not have one written down, that is the first finding, and it is a short conversation rather than a long project.
A finding from a real tenant
Hosts without cost-allocation tags
Scale
384
Impact
Chargeback impossible
Every finding ships with the source behind it and a CSV of the objects it found, so your team can re-run the check without us.

Questions we get about this domain

We tag in the cloud provider — is that enough?

Only where those tags are imported and preserved as Dynatrace tags. The check reports what exists tenant-side, which is where the alerting profiles and chargeback reports read from.

Can tags be applied automatically afterwards?

Yes, through automatic tagging rules, and that is usually the remediation. It is an implementation change rather than an audit output — the audit gives you the gap, the entity list and the rule that would close it.

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