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.
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.
- Leave a Comment |
- Mark review as helpful
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.
Rootly - a tool that lets you focus more on the Incident, and less on the Management
What do you like best about the product?
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.
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.
What do you dislike about the product?
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).
What problems is the product solving and how is that benefiting you?
The most valuable part of Rootly is how it streamlined AND standardized the incident process across departments. Cross-department communication is now automated behind workflows and incident attributes. An on-call engineer or SRE no longer has to page out to the on-call for an affected service manually. Our customer success team now knows precisely what contextual incident information is required to trigger an incident from Slack without having to remember or consult a Confluence wiki page. The right people are automatically informed for high-priority or visible incidents; participants are no longer required from an incident because someone missed a line in an escalation document or used the wrong method of communication.
Rootly has automated all the previously manual back-and-forth between folks with tribal knowledge and the respective tooling to notify, orchestrate, and review an incident.
Rootly has automated all the previously manual back-and-forth between folks with tribal knowledge and the respective tooling to notify, orchestrate, and review an incident.
Functional and flexible tool for incident management
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Rootly helps us manage our incidents. There are table stakes in this area that Rootly does well -- integrations, a slack bot, post-mortem guides, etc. It does all those just as well as its competitors, but the additional focus on the workflow engine and terraform integration has been really helpful. The main utility for us is that Rootly is a tool that allows us to encode our oncall process in a way reduces the cognitive load on our OCEs and supporting incident roles.
One example of this relates to our communication flow. We have many customers that have different needs and different business rules:
- "If it is a P1 incident for customer X, send emails to A, B and C. Send updates every 30 minutes"
- "If it is a P2 incident for customer X, send emails to A and B. Send updates every hour"
- etc for many customers
We've encoded these rules in various Rootly workflows and now our Comms Lead will get a slack notification with a sample email at the right time as the incident evolves, and can send this email with a single click.
One example of this relates to our communication flow. We have many customers that have different needs and different business rules:
- "If it is a P1 incident for customer X, send emails to A, B and C. Send updates every 30 minutes"
- "If it is a P2 incident for customer X, send emails to A and B. Send updates every hour"
- etc for many customers
We've encoded these rules in various Rootly workflows and now our Comms Lead will get a slack notification with a sample email at the right time as the incident evolves, and can send this email with a single click.
showing 1 - 10