Notifications
Clear all
Topic starter
12/06/2026 10:25 pm
TL;DR: Dynatrace dashboards, alerts, monitors, and metrics can now be backed up and restored through versioned snapshots as part of a cloud disaster recovery platform, reducing recovery time after misconfigurations, incidents, or ransomware, according to ControlMonkey. The real governance issue is not data loss alone but the loss of monitoring control plane state, which can leave teams blind when they most need observability.
NHIMG editorial — what this means for NHI practitioners
By the numbers:
Questions worth separating out
Q: How should security teams recover observability platforms after a configuration loss?
A: Security teams should treat observability recovery as a configuration restoration problem, not a rebuild from scratch.
Q: Why does observability configuration deserve the same protection as infrastructure?
A: Because configuration defines how the platform behaves during an incident.
Q: What breaks when monitoring settings are not recoverable?
A: What breaks first is trust in the monitoring layer.
Practitioner guidance
- Include observability configuration in disaster recovery scope Map dashboards, monitors, alerts, and metrics to the same recovery objectives used for cloud workloads and management tools.
- Define a known-good monitoring baseline Capture approved configurations for critical observability assets so teams can restore an intact alerting posture after accidental deletion or malicious change.
- Test restore workflows for monitoring platforms Run recovery drills that rebuild observability state from snapshots, not just infrastructure from templates.
What's in the full announcement
ControlMonkey's full post covers the operational detail this post intentionally leaves for the source:
- Step-by-step coverage of how Dynatrace configurations are discovered through secure APIs and stored as recoverable assets.
- Versioned snapshot handling for dashboards, monitors, alerts, and metrics, including what is preserved at each restore point.
- Operational workflow for recovering observability environments in minutes after deletion, misconfiguration, or ransomware.
- How the Cloud Resilience Dashboard surfaces backup readiness across cloud infrastructure and SaaS tools.
👉 Read ControlMonkey's Dynatrace configuration backup and recovery announcement →
Dynatrace configuration backup and recovery: what changes for teams?
Explore further
13/06/2026 1:11 am
Monitoring configuration is part of the operational identity plane, not an auxiliary admin setting. Dashboards, alerts, monitors, and metrics are the ruleset that tells teams what matters and when to respond. When that configuration disappears, the organisation still has tools but has lost the decision structure around those tools. Practitioners should therefore treat observability state as governed operational infrastructure, not disposable UI metadata.
A few things that frame the scale:
- A 30-min meeting will save your team 1000s of hours, according to The 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security.
A question worth separating out:
Q: Which teams should own observability disaster recovery?
A: Ownership should sit jointly with platform engineering, SRE, and security operations, because observability recovery affects both service continuity and incident response. The teams that manage the monitoring tools need to define snapshots, restore procedures, and access controls, while security leadership ensures those controls are tested and governed. If no one owns the recovery path, the monitoring plane becomes a single point of operational failure.
👉 Read our full editorial: Dynatrace configuration backup changes observability disaster recovery
