Rootly Reviews

My main use case for Rootly is on-call alerts. In my use case for on-call alerts, we plug into various applications using Rootly's out of the box plugins. If an alert triggers, Rootly is then responsible for alerting the engineer and it has all the paperwork as well that follows the incident.

Rootly has positively impacted my organization because before Rootly, we were missing alerts due to our legacy tool that was unable to call out engineers effectively. We occasionally missed alerts, but now we have achieved a 100% success rate of alert delivery, which is a massive step especially when trying to fix and identify these problems.

Regarding metrics or specific outcomes, we do not have noisy on-call alerts, but I would say we missed about three alerts a month previously, whereas now we miss zero.

The best feature that Rootly offers, which I really appreciated when we onboarded Rootly, is the shadowing feature. I evaluated quite a few tools but Rootly was the only one at the time that had this, and this allowed us to onboard new engineers into the on-call rota smoothly, which was a really cool feature.

Regarding how the shadowing feature helped with onboarding new engineers, rather than manually tweaking schedules to try to hack a way to shadow existing engineers, Rootly gave us a shadow feature which allowed us to say person X, please shadow person Y, using these times and these days, very customizable, and it allowed us to onboard people in a much more graceful manner.

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.

I have used Rootly for about two years.

Rootly is stable, and I have had no issues.

Rootly's scalability is fine; we are easily able to add new alerts. We manage our configuration by Terraform, which is a big touchpoint for us. If we ever need to add a new alert, we just put it into the code, run the pipeline, and we are done. The same applies for adding people; it is very easy.

Rootly's customer support is great; every time we have had to use it, they have gotten in touch with us really quickly and connected us to the relevant teams to fix our problems or potentially suggest a feature for the future. I would rate Rootly's customer support a 10, as there are no issues whatsoever.

We previously used Jira, the Atlassian suite. We switched because if we wanted the phone feature, we would have had to upgrade the whole organization's license to a premium license and that became very costly.

I am not certain about specific metrics, but we do not miss alerts anymore, so you could use that as a metric that it has effectively increased our reliability when handling incidents.

My experience with pricing, setup cost, and licensing was really easy. Rootly scheduled a call with us and was very quick to give us a POC license to trial out the full product. They were not pushy and we were able to have calls as and when needed, which was really good and we were able to onboard the tool quite efficiently.

Before choosing Rootly, we evaluated other options, including PagerDuty and Atlassian's premium version, along with Rootly.

I would rate Rootly a nine on a scale of one to ten. I give it a nine because nothing is perfect and there are always improvements that can be added. We have not used Rootly's AI capabilities yet. My advice to others looking into using Rootly would be to get in contact with them and try to get a POC set up because it speaks for itself; it is a brilliant tool. I am providing an overall review rating of nine for Rootly.

My main use case for Rootly is configuring it to follow up on all incidents inside the company, especially because Farmatodo has an e-commerce platform and we definitely have a lot of technical issues, both internal and client-related.

The main use case for Rootly was the visibility it provides, enabling us to create numerous dashboards with information related to the incident state, such as how many incidents we handled during a week or a month and the overall trends within the company.

Everyone in the company has access to Rootly via a public URL, so all people are aware of the number of incidents by each area, which I believe is the main use case.

Rootly helps me handle those issues by using a predefined template to define roles inside the workflow and utilizing a basic flow, which is very short in its lifecycle.

The most powerful feature of Rootly is its visibility; we can create a dashboard and integrate with Slack and Jira, for example, automating many steps in the follow-up process, which helps to centralize all communications around issues.

The best features Rootly offers include communication capabilities, particularly the integration with Slack, which stands out for me because it allows for very clean and direct communication with all clients and even with the resolution area.

The Slack integration helps my team by creating a specific resolution group and an automation channel inside Slack once an incident is opened in Rootly, ensuring that everyone knows when a new incident arises.

It is not just a notification; we create a group where all the relevant people can help solve the issue quickly.

The workflow capability of Rootly to create flows is another key feature for our operation, allowing us to establish specific rules for incidents in Jira or manage the metrics we need during the incident lifecycle, effectively automating many manual processes.

Rootly has positively impacted my organization, and we have measured its impact by analyzing the number of incidents we handle over a period.

With the strategic approach of putting everyone in a Slack group to resolve incidents, we have reduced the percentage of incidents created in a month by thirty percent during the first three months of using Rootly.

Other positive outcomes include time savings and improvements in collaboration; the groups inside Slack enable people to communicate across different areas and work directly with client operations, creating synergy and a strong integration between teams.

The integration process could be easier, perhaps with the addition of AI to facilitate smoother integrations with other applications, especially since those who manage integrations often need technical knowledge about web services and single sign-on processes, which can be challenging for non-technical users.

I would like to see an easier way to integrate Rootly with other applications, and if we can pay for a larger package that includes more integrations, that would be better.

I have been using Rootly for almost two years in my last job, which was with Farmatodo, a retail company.

Currently, I do not see any improvements needed for Rootly; I believe I have mentioned the most important features it provides for our company.

I chose a rating of eight out of ten because applications always have room for improvement and can offer new features over time, and in my personal opinion, it is a realistic assessment.

I did not have the opportunity to work with the AI capabilities inside Rootly, so I cannot comment on that aspect.

Regarding the accuracy and reliability of Rootly's AI output, I provide the same response; I have never used the AI capabilities within Rootly.

Rootly is deployed in my organization on a public cloud, specifically as a tenant in a public organization, allowing all technical team members access to their dashboards and performance, showing how many incidents occur over time.

I am not sure which cloud provider we use because we purchased a tenant directly from Rootly.

The communication capabilities of Rootly are its strongest point, and I believe this feature significantly improves our work by centralizing communication channels. I provided a rating of eight out of ten for this review.

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's best features include the Slack integration, which makes it easy to create, manage, and coordinate incidents without switching between multiple tools. Automatic incident timelines, stakeholder notifications, and status updates reduce manual efforts and help maintain consistency during incidents. Postmortem template and action item tracking simplify root cause analysis documentation and ensure follow-up tasks are captured efficiently.

Integration tools including Jira and ServiceNow help streamline the incident lifecycle. Rootly dashboard provides good visibility into active incidents, ownership, and incident metrics.

Rootly has positively impacted my organization by saving time with manually adding timelines, as they are already built in when timelines are added in Slack through integration. I can simply pin it, which is most secure and saves time. It also improves the resolution rate by tracking all data and timelines efficiently. Around twenty-five percent of the resolution rate has improved in the last six months. Rootly has saved my team time per incident with a twenty-five percent improvement in the resolution rate.

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.

I have been working in my current field for almost five years.

I advise others looking into using Rootly to invest time in configuring your incident workflow, integration, and postmortem templates upfront. This will help your team to get more value from Rootly by reducing manual efforts and improving coordination during incidents.

Rootly has been a valuable tool for managing critical incidents and problems management as well as postmortems. Its automation, Slack integration, and collaboration features have helped me streamline the incident response process. Continued enhancements to reporting, search capabilities, and AI-powered insights would make the platform even more effective. I would rate this solution an eight out of ten.

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.

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.

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.

I have used Rootly for about one year.

Rootly is stable.

Rootly's scalability is great; it goes under the hood and my colleagues and I as users do not think about it generally.

The customer support is quite good; I can write to Rootly specialists in Slack, and that is very useful.

We previously used ObsGenie, and we switched because ObsGenie is going out of service next year.

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.

My company does not have a business relationship with this vendor other than being a customer.

I have not seen a return on investment.

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.

Before choosing Rootly, we considered PagerDuty and iLert.

Rootly is a great solution for alerting, and I would recommend it. I gave this review a rating of 7.