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

Dynatrace Kubernetes monitoring audit: coverage, versions, recurring failures

Eleven checks on the cluster estate — which clusters are actually connected, which operator versions are behind, where workloads report without a cluster, and which failures repeat quietly every day.
Book a free audit All 71 checks

What these checks read

Cluster connection and operator version

Each connected cluster, its Dynatrace Operator version and its age against current. Old operators are the usual root of "monitoring stopped after the upgrade".

Workload coverage

Namespaces and workloads reporting no pods, and pods reporting no workload. Both shapes mean a gap the dashboard will not show as a gap.

Recurring pod and container failures

Restart loops and OOM kills that repeat on a schedule are usually read as noise. Counted over a window, they are a list of named workloads.

Cloud-native full-stack vs classic injection

Which injection mode each cluster runs, and where both are present at once — the configuration that produces duplicate entities and duplicate consumption.

Why it matters

Kubernetes is where monitoring coverage goes stale fastest. Clusters are created by teams that do not own observability, namespaces appear between audits, and an operator that was current at rollout is two minor versions behind by the time anyone looks.
These checks do not evaluate your cluster design. They answer a narrower question: does what Dynatrace believes about your clusters match what your clusters are. Where it does not, the finding names the cluster, the namespace and the workload, as a CSV — not a percentage.
The most common result is not a missing cluster. It is a cluster that is connected, reporting, green on every dashboard, and instrumented twice: once by the operator and once by a leftover init-container from the previous approach. Both sets of entities are real, both are priced, and neither is wrong enough to alert.

Questions we get about this domain

Does the audit run inside our clusters?

No. It reads the Dynatrace tenant through the API — the cluster entities, their versions and their reported events. Nothing is installed, nothing is scheduled, and no cluster credential is requested.

Will it tell us which workloads are not monitored?

It tells you which workloads Dynatrace can see and which report no running pods, plus namespaces with no instrumented workload at all. A workload in a cluster that was never connected is outside what any tenant-side audit can see — that gap shows up in the Coverage domain as a cluster count that does not match your own inventory.

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