
Rootly
Centralized on-call alerts have improved routing precision but still need better maintenance controls
What is our primary use case?
What is most valuable?
The best features Rootly offers include a very neat alert routine with quite precise rules and great entities. The precise rules and entities help me route alerts very specifically to the exact persons who are in charge and to rotate this person using on-call policies. This is implemented very comfortably in Rootly.
Rootly has positively impacted our organization because, in comparison to ObsGenie, the tool we used before Rootly, it is much more user-friendly, including the user interface and the whole approach to alerting and routing these alerts. Every maintainer is happy using Rootly after ObsGenie.
Since switching to Rootly, it has improved response time, and developers started really using the on-call system. Before, when we were using ObsGenie, developers did not like to use the on-call system, probably because of the user interface, as ObsGenie is not user friendly at all.
What needs improvement?
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.
For how long have I used the solution?
I have used Rootly for about one year.
What do I think about the stability of the solution?
Rootly is stable.
What do I think about the scalability of the solution?
Rootly's scalability is great; it goes under the hood and my colleagues and I as users do not think about it generally.
How are customer service and support?
The customer support is quite good; I can write to Rootly specialists in Slack, and that is very useful.
Which solution did I use previously and why did I switch?
We previously used ObsGenie, and we switched because ObsGenie is going out of service next year.
How was the initial setup?
Regarding my experience with pricing, setup cost, and licensing, we got a license for one year. Generally, it is great and the price is great, and that is the reason we chose Rootly. The only thing which is not comfortable is the change process for adding new users and licenses for them. It is not comfortable, so we decided to avoid it.
What about the implementation team?
My company does not have a business relationship with this vendor other than being a customer.
What was our ROI?
I have not seen a return on investment.
What's my experience with pricing, setup cost, and licensing?
Regarding my experience with pricing, setup cost, and licensing, we got a license for one year. Generally, it is great and the price is great, and that is the reason we chose Rootly. The only thing which is not comfortable is the change process for adding new users and licenses for them. It is not comfortable, so we decided to avoid it.
Which other solutions did I evaluate?
Before choosing Rootly, we considered PagerDuty and iLert.
What other advice do I have?
Rootly is a great solution for alerting, and I would recommend it. I gave this review a rating of 7.
Vital for Incident Management, Stellar Support
Friendly, Easy to Configure, Powerful and Highly Customizable for Incident Management
Easy Setup, Reliable Performance, and Helpful Support
Streamlined Issue Logging with Clean, Fast Functionality
Slack-Native Incident Management That Speeds Coordination
Teams recover from issues quicker because everyone knows the playbook and steps are automated.