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.
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.
- Leave a Comment |
- Mark review as helpful
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.
Rootly - Incident Management
What do you like best about the product?
Easy Incident Management from Slack
Integrations with the latest tools in the market.
Workflows are really flexible and useful to automate manual tasks with integrations.
Faster Response from the Rootly team for any questions.
Periodic product updates from the team
Integrations with the latest tools in the market.
Workflows are really flexible and useful to automate manual tasks with integrations.
Faster Response from the Rootly team for any questions.
Periodic product updates from the team
What do you dislike about the product?
Rootly can launch training modules/ videos to cover all the functionalities in their documentation
Rootly Web UI can be better
Rootly Web UI can be better
What problems is the product solving and how is that benefiting you?
Easy for Oncall Engineers to collaborate with the team during the entire Incident lifecycle
Rootly is going places
What do you like best about the product?
Rootly is a great incident management tool for that will streamline your process and take out a lot of the manual effort and toil when starting an incident. Rootly will keep you consistent which helps speed up the process to recovery. The team at Rootly is very responsive to customer feedback and they are constantly implementing new features based around that feedback. With Rootly, incident spin-up time has been reduced from minutes to seconds and it covers over 90% of our needs. Overall, Rootly is the best tool currently available in the market. They have a ton of integrations to get you started and workflows that are flexible enough to meet most of your needs. I have been super impressed with Rootly and the capabilities it offers. With the constant feedback loop, you won't regret giving them your money.
What do you dislike about the product?
Specific fields are essentially hardcoded, making it hard to customize around them. Rootly is working towards making these parts more customizable, but this does limit you in some ways. I wouldn't say this is a deal breaker, as most of the time, we can figure out a way around it. The other thing that is a bit lackluster is the UI, but don't really need or use it anyway. We don't want to context switch and try to operate from Slack whenever possible. Rootly is looking to address this to reduce some of the cognitive load when looking at the UI. The UI is just another item that is hardly a deal breaker.
What problems is the product solving and how is that benefiting you?
Rootly takes out the toil and makes incident management repeatable. They also have other tools to help keep track of metrics and get from incident response to postmortem in an automated way. This greatly helps in managing your incidents and seeing where in the process something is at.
Excellent Service
What do you like best about the product?
I greatly appreciate the responsiveness of the Rootly team. We were replicating an existing process in Rootly, so often when we identified an issue, it would end up being a blocker for us. Rootly was very attentive and quick to help us through each step and added functionality to address our rather specific needs. It can't be understated how helpful it is that those blockers are addressed so quickly to keep us moving.
What do you dislike about the product?
There are still some outstanding issues in Rootly, but based on prior experience, I expect they'll be fixed soon. One problem we seem to hit occasionally is that race conditions can exist in Rootly. This causes some pain and we have to be very careful to watch out for them.
What problems is the product solving and how is that benefiting you?
We are currently using Rootly primarly for its workflow capabilities. When an incident is reported, Rootly sets up the rooms and meetings we need.
Rootly's solid API makes it a good tool for power users
What do you like best about the product?
Rootly imposes structure on the incident response process, but is flexible enough to allow us to develop our own styles of workflows.
The well-thought-out API allows us to integrate it with other automations.
Full disclosure: I was offered a $100 gift card to provide this review. However, that's only enough to motivate me to do it; not enough to color my opinions.
The well-thought-out API allows us to integrate it with other automations.
Full disclosure: I was offered a $100 gift card to provide this review. However, that's only enough to motivate me to do it; not enough to color my opinions.
What do you dislike about the product?
Rootly is not very good at handling statefulness. It's virtually impossible to store, modify or retrieve custom information or variables related to an incident.
It is also rather difficult to manage your workflows. If you have a lot of them doing complex tasks, suddenly a small change could require you to edit dozens.
It is also rather difficult to manage your workflows. If you have a lot of them doing complex tasks, suddenly a small change could require you to edit dozens.
What problems is the product solving and how is that benefiting you?
Before Rootly, incident response could sometimes descend into chaos, with different responders handling the incident in idiosyncratic ways, storing evidence in the wrong location, etc.
Rootly allows us to keep IR organized and reduce confusion, which is particularly valuable when time is of the essence.
Rootly allows us to keep IR organized and reduce confusion, which is particularly valuable when time is of the essence.
Versatile and highly configurable incident management automation
What do you like best about the product?
Rootly has been a great asset in reducing the manual overhead of managing security incidents. It's extensive list of integrations means that we're quickly able to write automations for nearly all our existing internal tool suite, managing the entire lifetime of our incidents. These automations have saved us huge amounts of time, allowing us to focus on investigation and case quality rather than updating Jira tickets and managing Slack channels.
The Rootly API has been fantastic to deal with - it's allowed us to further integrate with our existing systems, allowing us to orchestrate changes in Rootly incidents. In our unusual use-case, being able to customise Rootly to our requirements and externally trigger changes has further minimised the manual incident management that must be done.
The Rootly team has been very receptive to our feature requests and is always willing to help improve our experience with our unusual use case. They've been very fast in developing and shipping changes to meet our project requirements and always make time to help us out as quickly as possible.
The Rootly API has been fantastic to deal with - it's allowed us to further integrate with our existing systems, allowing us to orchestrate changes in Rootly incidents. In our unusual use-case, being able to customise Rootly to our requirements and externally trigger changes has further minimised the manual incident management that must be done.
The Rootly team has been very receptive to our feature requests and is always willing to help improve our experience with our unusual use case. They've been very fast in developing and shipping changes to meet our project requirements and always make time to help us out as quickly as possible.
What do you dislike about the product?
Nothing to really call out here - the product was intended mainly for Site Reliability Engineering, however the Rootly team have been very open to feedback and willing to implement changes to fit our security incident management requirements.
What problems is the product solving and how is that benefiting you?
Rootly removes all the manual incident management that goes into running our security incidents. Not having to worry about things like inviting on-call engineers and sending out messages to leadership when high severity cases occur allow our Incident Response teams to focus on the response rather than the platform and people management aspects of running incidents. Since integrating fully with Rootly, our incident handling and documentation quality have increased significantly.
showing 11 - 20