Rootly Reviews & Product Details

Rootly is incredibly easy to use and configure, allowing us to streamline our entire incident management process. One of the standout features is the ability to create automated workflows, which saves a lot of time and ensures that key steps in the incident process are handled efficiently. For example, setting up automated reminders for SLA breaches or post-incident reviews is simple, and it keeps the team on track without manual intervention. The seamless integration with applications like Slack is another major benefit. We can manage almost the entire incident management process directly from Slack, from initiating incidents to updating timelines and coordinating with the team. This integration significantly improves communication and speeds up the resolution process. Review collected by and hosted on G2.com.

The main area for improvement is in the 'metrics' side of the application. Currently, there are some limitations around filters in certain panel options, which makes it harder to return the exact data we need for how we use the application. For example, it would be helpful if the graphs created within the metrics were more interactive. Ideally, users should be able to click on a specific data point, like the number of incidents between certain dates, and be taken directly to the relevant incident results. Improving this functionality would make Rootly even more effective in managing and analysing incident data. Review collected by and hosted on G2.com.

A few things I like so far:

- Easy to use with a great slack interface

- Has an API which allows me to use Rootly's data when I eventually want to work with this data programatically

- Although we don't use this feature, there's the ability to incorporate with JIRA which makes issue tracking for action items easier

- Anytime I've found a bug I can work with rootly's support team to get the issue resolved quickly

- Review collected by and hosted on G2.com.

Not too many things to dislike, but things I would love:

- More automation around incident retros - automating creating meetings based on participent's gmail calendar would be sick. Even though we have manditory retros with our workflow, those are often skipped, meaning we lose the valuable lessons learned during an incident.

- This may be a limitation of slack, but a clearer UI demarkation of who is playing which role in an incident would help users' tell who is playing which role in an incident Review collected by and hosted on G2.com.

Rootly Team frequently checks in and provides required support at every stage, this enhances our experience positively. Communication is easy via the Slack support channel.

Product Workflows - Workflows are made easy for everyone to easily understand, providing great UX.

Feature requests shared are taken seriously and they ensure they meet the expectations. Collaboration with the team is great. The best part is - Direct support from the founders when necessary.

We were handling everything manually earlier, once we onboarded with Rootly, our team saved at least 2 hours a day. There is not even one day without using Rootly. Integration with multiple tools is simplified, especially JIRA.

Given these points, adapting to Rootly was made easy, and moving to another similar tool was made unthinkable. Review collected by and hosted on G2.com.

I would say NOTHING! Given the fact we are using Rootly after handling everything manually, our experience with them is amazing. Review collected by and hosted on G2.com.

Rootly is an amazing beginning, and is getting better quickly. Each week they release updates, improvements and features that expand their capabilities, and it gets easier and easier to use.

Initial implementation takes some work, but their team is there to help. The support they provide is excellent, and the troubleshooting is mostly fast, direct and responsive.

I use the product for several hours a day, and have quickly become familiar with the feature set. It's made conversations about our incident system more powerful, provided data where it was needed most, and allows us the insight necessary to improve our processes. Review collected by and hosted on G2.com.

The integrations with Confluence, Jira, PagerDuty and Slack are decent. There is room for improvement in all of them, but they get most tasks done and done right.

Custom forms and fields are a weak point (they are available but take significant hand holding in the product to make effective), and the reporting systems are "fine", but once again require quite a bit of manual labor to build and maintain. Review collected by and hosted on G2.com.

Rootly stood out as having the most number of integrations that are actually useful. It is simple, easy to use, yet highly customizable to your organization. We use it everytime there is an active incident - in fact, we have made Rootly the starting point of our organization's incident response process.

The turn around time in fixing bugs are usually low (sometimes to the tune of hours instead of days). Not to mention, their customer facing team are all friendly, easy going, and highly responsive. I would pick Rootly for their people alone. Review collected by and hosted on G2.com.

Rootly's analytics/reporting feature and Confluence integration is not as polished as it can be. This is not a deal breaker though as you can easily exfiltrate Rootly data to your own data warehouse for reporting. Their Confluence export of retrospective can be further improved, this is especially around the Slack timeline feature where it is sometimes incomplete or in the incorrect order. Slack screenshots are also not embeded in the Confluence doc. Review collected by and hosted on G2.com.

After a couple of false starts with other tools, we finally found Rootly. The ease of use to get started running incidents stood out to me. As a fast growing startup, we needed to get going fast. My team was able link all our critical incident tooling into Rootly & build in the automation we needed in minutes. Review collected by and hosted on G2.com.

It solves our pain points around incident automation. Nothing to complain about. We’re excited to see what the team comes up with this year. Review collected by and hosted on G2.com.

First and foremost incidents are about communication, both internally and externally, and it was important to us at ROLLER that any tool we chose for incident management fit within our existing methods of communicating. Rootly with its deep integration with Slack fit the bill perfectly, removing the problem of disjointed conversations happening across different platforms that we had previously.

Despite taking an unusual approach of being support-led in our incident creation, essentially allowing anyone to "pull the fire alarm", we were easily able to replace our cobbled-together custom webhooks with simple workflows that integrated with our existing tools, such as Jira, Opsgenie and Datadog. We were even able to repurpose a lot of the existing workflows that are available as soon as you first log into Rootly, a sign that the team has carefully considered each integration and how it will work inside Rootly.

So far on our journey together, Rootly has improved incident ownership, mean-time to resolution and allowed for more effective communication for our geographically disparate teams. It has quickly become a vital tool for helping to keep our services up and running for our customers. Review collected by and hosted on G2.com.

The initial setup can be a little bit slow when your company already has a prescriptive incident workflow that you want to replicate inside Rootly. That said, it appears the team at Rootly was aware of this as they have released a Terraform plugin for configuring your workflow as code which would address this problem perfectly. Review collected by and hosted on G2.com.

During the initial evaluation, we compared Rootly against a variety of tooling that offered similar functionality. What was important was that we had a reliable and heavily customizable tool that also worked "out of the box" for processes we either didn't care to customize or that we used another vendor for (e.g., alerting via Pagerduty). Rootly met these requirements and more.

We were able to set up custom workflows that would trigger based on a variety of incident attributes. With near-unlimited dimensionality/cardinality for incident attributes, we could use Rootly to automate processes that severely slowed down the incident investigation process. Furthermore, Rootly has rich integration with all of our other tools. In the case the integration didn't exist yet, Rootly went out and built it out for us. Combining the workflows, incident attributes that could determine which workflow(s) to run, and rich tooling integration meant that we spent less time figuring out what to do for different incident types and more time investigating the incident.

Finally, Rootly is backed by a spectacular team eager to deliver. Working with Rootly feels like a partnership; as we continued to use their tool and found more use cases, our feature requests quickly found their way into (or, luckily for us, were already in) their backlog. Whether it was quality-of-life improvements to aid incident visibility on Slack (rich customization of Slack messages from Rootly) or Infrastructure-as-Code management for workflows via Terraform, Rootly continued to iterate and grow with our needs. Review collected by and hosted on G2.com.

With heavy customization comes a large amount of complexity when navigating the workflows. Rootly has done a lot of work improving this; visually via workflow groups and organizationally by adding a Terraform provider to store workflows as code. However, it is still daunting when opening the Workflows tab and seeing dozens of workflows. The large number of workflows is because workflows do not have strong conditional logic (e.g., notifying different teams based on an affected service results in a workflow for each team, rather than a single workflow with branching conditions). Review collected by and hosted on G2.com.

There are two key areas we like:

1) The workflow engine in Rootly is really powerful. We've been able to encode a complicated set of communication requirements in a way that helps our OCEs manage the incident and not spend time looking up complicated business rules before communicating to customers.

2) The terraform support is tremendous -- nearly everything in Rootly is configurable via the terraform provider. This means we can manage our oncall tooling the same way we do our other infrastructure.

This has been backed by a very responsive and friendly development team. Review collected by and hosted on G2.com.

We've barely scratched the surface of what we can do with Rootly. In some ways it is maybe a little too flexible; we haven't been able to sit down and fully customize everything to our liking or even internalize everything it can do. Review collected by and hosted on G2.com.

Rootly synchronizes really with Slack and it's amazing that the entire incident lifecycle from the beginning of a new incident until an incident is resolved can be managed via different commands inside Slack.

The interface is very basic, simple, and customizable and that's what makes it good. Each organization can decide and set up the exact fields (or use the existing ones) that are relevant to their Incident Management process.

The Rootly Support team has been active and helpful when it comes to any technical question. New ideas are positively welcomed.

Rootly has very clear and easy to use guidelines, helpful descriptions and that enables people with little to no previous experience in Incident Management to jump straight into creating their first incident! Review collected by and hosted on G2.com.

Depending on the size of the organization the workflow and automation management can become overwhelming for a single individual if the amount of automation/workflow rules grow large. Thankfully, Rootly has the option to group different workflows under different folders/categories (Slack, Jira, Pagerduty etc.). Review collected by and hosted on G2.com.