ControlMonkey is expanding its cloud configuration disaster recovery platform to include observability environments, adding support for tools like Datadog, New Relic, Dynatrace, Grafana Cloud, and Splunk. The update brings daily snapshots and recovery capabilities for dashboards, alerts, and monitoring configurations—areas that are typically not covered in disaster recovery plans.
For MSPs, observability platforms sit at the center of incident response and management. They are the first place analysts look when something breaks. If dashboards, alert rules, or escalation policies are missing or misconfigured, response slows down across every tenant. What’s changing here is that observability is now being treated as part of the recoverable control plane, not just a monitoring layer. That creates an opportunity for MSPs and MSSPs to expand beyond detection and response into recovery readiness as a managed service.
From tool visibility to service delivery
ControlMonkey’s model focuses on continuously capturing configurations and storing them as versioned snapshots that can be restored when needed.
Amir Regev, Global Director of Partnerships and Cloud Alliances at ControlMonkey, explained to ChannelE2E, “ControlMonkey is built for configuration disaster recovery, not just for backup, code management, or visibility. The key difference is that we do not stop at showing changes or storing templates - we continuously capture the exact infrastructure configuration, convert it into deployable definitions, commit each snapshot as a versioned record in the customer’s Git, and enable recovery of individual resources or full environments.”
For MSPs and MSSPs, that shifts the conversation from tooling to outcomes. Instead of relying on customers to maintain accurate infrastructure-as-code, the platform captures real-world environments as they exist.
“We also account for resources managed and unmanaged by IaC, which is critical because many production changes happen outside Terraform,” Regev adds. That gap shows up often in managed environments, where drift accumulates across tenants and tools. “Traditional backup tools are primarily about data and workload recovery, while IaC tools depend on the assumption that the environment is already fully codified and up to date. In reality, many teams discover during an incident that they do not know what actually existed, cannot reliably reconstruct infrastructure state, and are forced into manual recovery under pressure.”
What changes during an incident
For MSSPs running multi-tenant SOC operations, the difference becomes clear during incidents. Observability tools can show what changed, but they do not restore the environment.
As Regev puts it, “In a real incident, the question is not ‘can I see what changed?’ It is ‘can I restore the environment, correctly, fast, and with confidence?’”
ControlMonkey’s approach is designed to support that outcome at scale. “We maintain daily configuration snapshots, store them as versioned recovery points, and support recovery with dependency handling and ordering so teams are not stitching together a response manually during an outage or ransomware event.”
That matters in multi-tenant environments where dependencies span identity, networking, and monitoring layers. “Real incidents are blocked by missing dependencies: Route 53, IAM, identity providers such as Okta, networking policies, dashboards, monitoring policies, CDN and edge settings,” Regev notes. “Observability can help you identify impact; it does not by itself give you a clean, repeatable mechanism to rebuild those configurations as a known-good state.”
A new layer in the MSP/MSSP stack
From a channel perspective, this is not another monitoring capability. It introduces a recovery layer that sits above individual tools and tenants.
“For an MSSP, the unique value is that ControlMonkey provides a multi-tenant control and recovery layer, not another monitoring surface,” says Regev. “The platform is positioned around one control plane for many customers, with governance, guardrails, Git-centric workflows, and integrated operations that fit managed-service delivery models.”
That has direct implications for service packaging and margins. “It is built to help partners manage more customers with current staff, create recurring resilience and remediation workstreams, and deliver clear audit evidence and DR-readiness reporting across customer estates,” he adds.
In practice, this gives MSPs and MSSPs a way to standardize recovery across customers instead of relying on tenant-by-tenant processes. “Customers do not just need alerts or change logs inside one observability stack. They need confidence that their cloud and third-party configurations are actually recoverable… ControlMonkey’s value is that it gives MSSPs a standardized way to discover what exists, show what is and is not protected, and execute repeatable configuration recovery.”
Where this fits in the broader shift
The bigger shift here is how disaster recovery is being defined in managed services. It is no longer limited to restoring data or workloads. Configuration - across infrastructure, identity, network, and observability - is becoming part of the service responsibility. This opens up a new category: continuous configuration recovery and resilience as a service. It also raises expectations. Customers will expect not just visibility and response, but proof that their environments can be rebuilt quickly and consistently. This update signals where the market is heading. Recovery is moving closer to day-to-day operations, and MSPs/MSSPs that can operationalize it across tenants will have a clearer path to scalable, repeatable service delivery.
