Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Streamlined Incident Management with Great Automation and Support.
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Rootly helps us solve the challenge of managing incidents efficiently by automating key parts of the incident management process. It enables us to streamline everything from incident creation to resolution, ensuring that nothing falls through the cracks. With its seamless integration into Slack, we can manage incidents in real-time and keep our teams aligned, reducing communication delays.
One of the biggest benefits has been a significant improvement in our incident metrics. Rootly has directly contributed to reducing our Mean Time to Detect (MTTD), Mean Time to Mitigate (MTTM), and Mean Time to Resolve (MTTR) stats. Automation and clear workflows allow us to respond faster and work more effectively as a team. Additionally, Rootly’s automation enables us to update our status page in real-time, ensuring that our customer base is kept informed throughout the entire incident process without manual intervention. This keeps communication clear and efficient.
The ability to automate SLA reminders, incident escalations, and post-incident reviews further enhances our incident management process, helping us stay on top of every incident and respond swiftly.
One of the biggest benefits has been a significant improvement in our incident metrics. Rootly has directly contributed to reducing our Mean Time to Detect (MTTD), Mean Time to Mitigate (MTTM), and Mean Time to Resolve (MTTR) stats. Automation and clear workflows allow us to respond faster and work more effectively as a team. Additionally, Rootly’s automation enables us to update our status page in real-time, ensuring that our customer base is kept informed throughout the entire incident process without manual intervention. This keeps communication clear and efficient.
The ability to automate SLA reminders, incident escalations, and post-incident reviews further enhances our incident management process, helping us stay on top of every incident and respond swiftly.
- Leave a Comment |
- Mark review as helpful
Convenient tool for incident management in slack with great features
What do you like best about the product?
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
-
- 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
-
What do you dislike about the product?
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
- 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
What problems is the product solving and how is that benefiting you?
Acting as the hub to the incident management process
Product with amazing capabilities and wondering TAT for anything
What do you like best about the product?
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.
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.
What do you dislike about the product?
I would say NOTHING! Given the fact we are using Rootly after handling everything manually, our experience with them is amazing.
What problems is the product solving and how is that benefiting you?
- Incident Management.
- Oncall Escalations.
- Oncall tasks.
- Manage multiple Bugs within the product.
- Easier Reporting.
- Easy to collaborate.
- Oncall Escalations.
- Oncall tasks.
- Manage multiple Bugs within the product.
- Easier Reporting.
- Easy to collaborate.
I would choose Rootly for the people alone
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Rootly has quickly become the starting point of our incident response process. It automated our 25 steps process down to 5 steps which significantly lowered the barrier to manage incidents.
Excellent start, and rapidly maturing product
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
It provides us with data where there was none, allowed us to standardize our process, and has increased the automations that let our incident response team focus on responding and not on managing a third party product.
Rootly got us up and running fast!
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Rootly helps ensure that our whole team is on the same page, quickly, during an incident. The start of an incident is crucial for us (as I’m sure it is for others), and Rootly gets us ready fast.
It also helps ensure we follow our process consistently. We’ve seen a solid reduction in our MTTR metrics and the team is more confident than ever in their ability to respond to incidents.
This year we’re looking forward to pushing automated communication even further to ensure partners & other internal stakeholders have all the information they need when we are responding to an incident.
It also helps ensure we follow our process consistently. We’ve seen a solid reduction in our MTTR metrics and the team is more confident than ever in their ability to respond to incidents.
This year we’re looking forward to pushing automated communication even further to ensure partners & other internal stakeholders have all the information they need when we are responding to an incident.
Incident management that fits your workflow
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Rootly allows us to focus on the issue at hand when we have an incident by removing a lot of the laborious tasks required when resolving an incident. It does this via simple commands and reactions in Slack, automation and integration with a lot of other popular tools used during the lifecycle of an incident. It even pre-populates an incident timeline to be included in the postmortem, saving you time after the incident is resolved.
Rootly makes running incidents in Slack so easy
What do you like best about the product?
Rootly makes running incidents in slack easy so you can concentrate on fixing the incident. Rootly has been a critical help and responsive in helping to create and manage incidents through slack.
What do you dislike about the product?
I love everything about Rootly. Rootly has been a great partner to work with from the beginning. Rooltly has always listened to our feedback and has provided fixes when necessary.
What problems is the product solving and how is that benefiting you?
Rootly is a highly customizable solution for incident management. Rootly has helped us get the people working on the incidents so we can get the incidents solved.
Rootly - excellent incident management system
What do you like best about the product?
Rootly has significantly simplified and streamlined our incident management process. It's enabled us to automate a lot of manuaal tasks and ensure consistent incidents management. It allows us to easily build out our workflows and provide automations to our response team. It's also very helpful post incident, helping automate the post incident review process, building timelines and open action items.
What do you dislike about the product?
Currently limited to 1 channel per incident. Occasionally we need multiple channels per incident. Aside from that's it been fantastic.
What problems is the product solving and how is that benefiting you?
Ensuring consistent incident management process and automating response tasks and note taking. This has significantly reduced the amount of manual workload creating channels and following tasks lists.
Rootly simplifies our incident management
What do you like best about the product?
Rootly makes incident management easier with it's Slack integration and they get the needs of a Saas platform incident management system.
What do you dislike about the product?
We've been loving it so far and haven't come across any issues yet.
What problems is the product solving and how is that benefiting you?
We do most of our comms and incident management on Slack anyway. Having Rootly deeply integrated with Slack meant that there was seamless communication between the teams during an incident and more focus can be put onto the resolution of the event rather than trying to update all stakeholders.
showing 1 - 10