Lead Dev Ops Engineer at a financial services firm with 51-200 employees
Real User
Top 10
Sep 29, 2026
The team at Rootly seems to always be adapting and looking at what the market is doing and adding new features, so for us, Rootly currently fits the bill. If there was something we needed, we could reach out to the team at Rootly and they would add it to their roadmap. I do not think there are any improvements needed for Rootly that I haven't already mentioned; overall, I am really happy with the product.
There are a few areas where Rootly can be improved. More customization options for postmortem templates and reports would be helpful. Enhancing search functionality to make it easier to locate historical incidents and action items would be beneficial. Better reporting and analytics for recurring incidents and SLA trends would improve problem management. Additionally, flexibility in notification settings and workflow customization would benefit organizations with different incident processes.
Devops engineer at a tech vendor with 51-200 employees
Real User
Top 5
Jun 9, 2026
Regarding improvements for Rootly, first of all, it would be great to make comfortable maintenance mode, as it does not let me silence alerting comfortably. This is one of a very small list of points which were better in ObsGenie. The maintenance mode could be improved. The second point is a mobile application; if I have it on two devices, it does not send the notification to both of them. It sends the notification to only one. It would also be great to improve the regular expression configuration in alert rules. Regarding Rootly's AI capabilities, we had one incident when we lost alerting generally because Rootly crashed, and we did not like it. This happened because Rootly does not have a multi-cloud environment. I do not know how it is implemented currently, but it was a very bad experience.
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.
The team at Rootly seems to always be adapting and looking at what the market is doing and adding new features, so for us, Rootly currently fits the bill. If there was something we needed, we could reach out to the team at Rootly and they would add it to their roadmap. I do not think there are any improvements needed for Rootly that I haven't already mentioned; overall, I am really happy with the product.
There are a few areas where Rootly can be improved. More customization options for postmortem templates and reports would be helpful. Enhancing search functionality to make it easier to locate historical incidents and action items would be beneficial. Better reporting and analytics for recurring incidents and SLA trends would improve problem management. Additionally, flexibility in notification settings and workflow customization would benefit organizations with different incident processes.
Regarding improvements for Rootly, first of all, it would be great to make comfortable maintenance mode, as it does not let me silence alerting comfortably. This is one of a very small list of points which were better in ObsGenie. The maintenance mode could be improved. The second point is a mobile application; if I have it on two devices, it does not send the notification to both of them. It sends the notification to only one. It would also be great to improve the regular expression configuration in alert rules. Regarding Rootly's AI capabilities, we had one incident when we lost alerting generally because Rootly crashed, and we did not like it. This happened because Rootly does not have a multi-cloud environment. I do not know how it is implemented currently, but it was a very bad experience.