I use Rootly every day to manage the end-to-end incident lifecycle. When a critical incident is reported, I create or join an incident on Rootly, assign the appropriate severity, and engage the required engineer to support the team through Slack. I use the platform to track incident updates, maintain an accurate timeline, assign responders, and send timely internal and stakeholder communications. Once the issue is resolved, we mitigate or resolve the incident. I use Rootly to schedule and document the postmortem, capture the root cause analysis, and action items if there are any. As a critical incident manager, I use Rootly to create incidents and assign the appropriate severity level. There was a recent issue with the Salesforce access application where multiple employees were unable to log in to the platform and perform their daily work. I used Rootly to create an incident and assign the appropriate severity automatically. The dedicated Slack incident channel was created automatically, which is beneficial as Rootly integrates with Slack. After creating the incident, I engaged the respective on-calls while tracking the investigation by maintaining a live incident timeline with updates from all the engineering teams, coordinating communication between technical teams and stakeholders, and sending timely internal and end-user communications at key milestones, including the incident acknowledgment, mitigation, and resolution or restoration times. I recorded key timestamps such as impact start, detected, mitigation, and resolution in Rootly. After Rootly incident was marked resolved, I scheduled a postmortem with the documentation already built into Rootly. The documentation is built in with all the details, which I filled such as root cause, mitigation, long-term fix, or permanent fix in Rootly postmortem template. Following the completion of the postmortem meeting, I went back to Rootly ticket to create action items, assign them to the owner, and assign due dates to ensure completion. Using Rootly helped keep all responders aligned in one place, reduce manual coordination, maintain a complete audit trail of the incident, and ensure the post-incident review and action items were completed efficiently.
Devops engineer at a tech vendor with 51-200 employees
Real User
Top 5
Jun 9, 2026
Rootly is our central system for on-call and alert management. We route alerts from Alertmanager to Rootly, and after that, we route alerts from Rootly to different teams that are in charge of the services they maintain.
Rootly is an essential tool for effectively addressing and managing incidents within any system or organization. With quick and reliable incident alerts, comprehensive incident management capabilities, and efficient problem-solving features, Rootly helps users to identify, prioritize, and resolve incidents, resulting in improved system reliability and reduced downtime. The solution is highly regarded for its reliability, excellent customer support, and overall value to users.
I use Rootly every day to manage the end-to-end incident lifecycle. When a critical incident is reported, I create or join an incident on Rootly, assign the appropriate severity, and engage the required engineer to support the team through Slack. I use the platform to track incident updates, maintain an accurate timeline, assign responders, and send timely internal and stakeholder communications. Once the issue is resolved, we mitigate or resolve the incident. I use Rootly to schedule and document the postmortem, capture the root cause analysis, and action items if there are any. As a critical incident manager, I use Rootly to create incidents and assign the appropriate severity level. There was a recent issue with the Salesforce access application where multiple employees were unable to log in to the platform and perform their daily work. I used Rootly to create an incident and assign the appropriate severity automatically. The dedicated Slack incident channel was created automatically, which is beneficial as Rootly integrates with Slack. After creating the incident, I engaged the respective on-calls while tracking the investigation by maintaining a live incident timeline with updates from all the engineering teams, coordinating communication between technical teams and stakeholders, and sending timely internal and end-user communications at key milestones, including the incident acknowledgment, mitigation, and resolution or restoration times. I recorded key timestamps such as impact start, detected, mitigation, and resolution in Rootly. After Rootly incident was marked resolved, I scheduled a postmortem with the documentation already built into Rootly. The documentation is built in with all the details, which I filled such as root cause, mitigation, long-term fix, or permanent fix in Rootly postmortem template. Following the completion of the postmortem meeting, I went back to Rootly ticket to create action items, assign them to the owner, and assign due dates to ensure completion. Using Rootly helped keep all responders aligned in one place, reduce manual coordination, maintain a complete audit trail of the incident, and ensure the post-incident review and action items were completed efficiently.
Rootly is our central system for on-call and alert management. We route alerts from Alertmanager to Rootly, and after that, we route alerts from Rootly to different teams that are in charge of the services they maintain.