
See how Cutover Respond, powered by intelligent AI agents, revolutionizes incident management by transforming reactive responses into proactive solutions. Watch how you can lower your mean time to resolution and coordinate complex recoveries with speed and precision.
In today's complex technology operations landscape, being able to quickly and effectively respond to incidents and recover from disasters is critical. When incidents occur, coordinating complex responses can be overwhelming. Manual processes, fragmented communication and human error can lead to costly delays and disruptions. With Cutover Respond combined with Cutover AI's AgenScik models, we are revolutionizing incident management. In this video, you will see how you can transform reactive responses into proactive intelligent solutions. Let's take a deeper look at how CutOverAI and CutOverRespond can lower your mean time to resolution. An incident is generated for the cloud workload and the IBM app in Dynatrace and has been logged in ServiceNow. Because this is a mission critical application, the incident has been escalated to a high priority case. As Cutover Respond is tightly integrated to ServiceNow, we have a new Active Respond incident created. Because I am logged in as an incident manager, I can see we have an active incident. A live runbook has auto started and sent out initial communications, in this case via Microsoft Teams, to get people mobilized in this incident. Because of CutOver's flexibility, any communication tool sets can be used, such as Zoom, Slack, Microsoft Teams, or SMS. Here we can see that the Any IBM workload in AWS is down and a further app in Azure is showing a degraded status. Within Respond, you can request recent changes for the application to get more details to see what has happened. In this case, the application should be failed over to another site. Linking over the cutover application metastore, we can see there is an approved runbook for the Annie IBM app in AWS. However, we also see there is no template for the asset application in Microsoft Azure. In this instance, we can easily click the Create button and generate a runbook for this app, or all the apps with missing cloud based templates. Going back to Cutover Respond, we can see the AnyIBM recovery process has already begun because of the integration to Dynatrace and pulling in that runtime data. As the Incident Manager owner, you want more situational awareness on the outage before you actually fail over the application. Using CutOver's agentic AI capability, this AI agent can make a request to view potential issues from your application monitoring platform, or in this demo to make requests to ServiceNow to get the five most recent changes for the five most recently created CIs in AWS. For the asset IBM app, we could do the same with Remedy and Azure. In addition, we also have agentic AI tasks requesting the service status for the five most recently created CIs. The advantage with CutOver is you can build trust into your AI process, gaining you confidence. Cutover allows you to see exactly what the AI agent derived, its intended plan, and the actions it performed. Because the AI agent return data did not highlight any changes to the CIs and only the AnyIBM workload in AWS was down, we are going to failover that application to a secondary availability zone. Before we begin the failover, we want to check that the standby AWS cloud location is ready to accept traffic. As we move through the tasks, we have integrated Lambda functions to spin up a new instance on the secondary site on AWS. To keep an eye on progress, the Incident Manager and other stakeholders can view in real time all progress with the failover. Now that the failover runbook has finished, we can see that we missed our recovery time objectives with Cutover's RTO RTA calculation for the Annie IBM app. Using Cutover AI's improved functionality, we can quickly get suggested areas to improve the runbook recovery plan for future failovers. Now that the incidents of the Annie IBM app has been failed over, we can go back to Cutover respond and mark the incident as mitigated, which will update the ticket in ServiceNow. To close this out, the incident management team can do forensics with runbook snippets to work on and identify a root cause and fully resolve this scenario. Finally, the immutable activity feed can also serve as an audit log for any regulatory reporting. To learn more about Cutover Respond and AI, visit cutover dot com and book a demo today.