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.
Great tool for our organization
What do you like best about the product?
Simple to use: manage incidents in slack where most of the activity happens anyways
What do you dislike about the product?
We haven't encountered any major issues so far
What problems is the product solving and how is that benefiting you?
We manage all of our incidents as well as post-mortem in rootly. We've been much more consistent in our post-mortems and information capture during incidents
Recommendations to others considering the product:
Rootly is a great tool for organizations that are serious about incident management.
- Leave a Comment |
- Mark review as helpful
Rootly Adds Simple Automation To Incident Management Without Large Process Changes
What do you like best about the product?
We've always used Slack to manage incidents and wanted to add some very light structure and automation. Rootly:
1. Didn't require a significant change to our process, we simply call `/rootly new` instead of creating a new channel and select 4-5 options around severity etc.
2. Makes it very easy to add automation and nudges
3. Lets us access data about our incidents in a structured way for dashboards etc.
This has been very easy to set up and a pleasure to use. The rootly team has also been very responsive to feature requests which have allowed us to really fit the tool into our use case.
1. Didn't require a significant change to our process, we simply call `/rootly new` instead of creating a new channel and select 4-5 options around severity etc.
2. Makes it very easy to add automation and nudges
3. Lets us access data about our incidents in a structured way for dashboards etc.
This has been very easy to set up and a pleasure to use. The rootly team has also been very responsive to feature requests which have allowed us to really fit the tool into our use case.
What do you dislike about the product?
Rootly is a fairly new piece of software and some use cases don't feel all the way ironed out yet (eg. the workflow automation tool doesn't fully support all the actions I'd expect). This is significantly mitigated by the strong responsiveness to feature requests and the great support we've received.
What problems is the product solving and how is that benefiting you?
1. Our incidents are now available in a structured format for us to query
2. Our incidents how to have helpful nudges which encourage engineers to manage them effectively
3. Minor tasks like writing a post mortem timeline, closing channels after incidents are resolved, notifying our bugs-critical channel, etc. are now fully automated which saves time and increases consistency
2. Our incidents how to have helpful nudges which encourage engineers to manage them effectively
3. Minor tasks like writing a post mortem timeline, closing channels after incidents are resolved, notifying our bugs-critical channel, etc. are now fully automated which saves time and increases consistency
A fresh and innovative approach to incident management
What do you like best about the product?
What stands out for Rootly as an incident management tool is that it understands the core problem around incident management which is around important integrations and understanding the way teams work around an incident. One of the key features that attracted me to choosing Rootly was its Slack and Datadog integration along with the ability to report back on incidents.
What do you dislike about the product?
There's a lot more positives than downsides to Rootly but i'd definitely would like to see them refine their workflows, searching and ticket tracking feature.
What problems is the product solving and how is that benefiting you?
Rootly solved the problem of having an incident management tool that integrates well with Slack. We rely heavily on Slack as part of our day to day and to have a tool that nicely integrates with this alongside other tools that we use to monitor our applications, Datadog, makes it the best choice for incident management. There's a lot of benefits to using Rootly, aside from easy integration, being able to automatically set up workflows that integrates with our issue tracker, there's the added benefit of being able to manage incidents more smartly with the combination of everything put together in a single location from teams, action items, workflows all the way through to post mortem incidents. Rootly understands all the features that are needed for teams to be able to navigate and learn from an incident effectively.
Rootly has made our incident management significantly more efficient/reliable
What do you like best about the product?
Many things. I'll list them:
1) The tool is incredibly simple to onboard into. The flow is intuitive and I can run through a whole demo and onboard new teammates into the tool in 10 minutes.
2) Being able to distinguish between mitigation time and resolution time helps improve our reporting. Since everything is happening in Slack, we've seen that teams are significantly better at adding resolution notes, as well as closing out incidents when they need to be closed out -- which leads to improved accuracy in our MTTR tracking.
3) Integrates with all of our other core incident management tools (for example: paging on-call, our ticketing system) so we were able to integrate it with our existing workflows.
4) A lot of our previously manual tasks (for example: starting an incident video call) are now automated, which makes our incident workflow a lot more reliable week over week despite a rotating on-call shift. And then some of our previous tasks we were relying on other tools to automate -- can now all be automated through Rootly, which gives me more confidence in our alerting flows.
5) We've had several instances where we needed a specialized feature or additional support for our specific team's needs. Their team is so incredibly responsive it's hard to put into words. They've addressed our questions with real solutions instead of interim workarounds, and have even hopped on calls to review our questions and work out things together.
1) The tool is incredibly simple to onboard into. The flow is intuitive and I can run through a whole demo and onboard new teammates into the tool in 10 minutes.
2) Being able to distinguish between mitigation time and resolution time helps improve our reporting. Since everything is happening in Slack, we've seen that teams are significantly better at adding resolution notes, as well as closing out incidents when they need to be closed out -- which leads to improved accuracy in our MTTR tracking.
3) Integrates with all of our other core incident management tools (for example: paging on-call, our ticketing system) so we were able to integrate it with our existing workflows.
4) A lot of our previously manual tasks (for example: starting an incident video call) are now automated, which makes our incident workflow a lot more reliable week over week despite a rotating on-call shift. And then some of our previous tasks we were relying on other tools to automate -- can now all be automated through Rootly, which gives me more confidence in our alerting flows.
5) We've had several instances where we needed a specialized feature or additional support for our specific team's needs. Their team is so incredibly responsive it's hard to put into words. They've addressed our questions with real solutions instead of interim workarounds, and have even hopped on calls to review our questions and work out things together.
What do you dislike about the product?
I'm only adding this in because this is a required question, I would say the one thing I would change is being able to have a better 2-way sync with ticket management systems. For example: changing a ticket in Asana would change the ticket in Rootly, and creating a ticket in Asana would automatically start the Rootly flow. I will say, the second example was a requirement for our team's flow and we were able to work with their engineering team on achieving this through webhooks and API calls.
What problems is the product solving and how is that benefiting you?
Rootly is a great solution for a problem that is familiar to many of us: creating an easy-to-understand, automated, and trustworthy alerting workflow for incidents so that engineers can address incidents appropriately and collaboratively, and that employees/clients can feel confident that incidents are being addressed immediately.
It's made me significantly more comfortable that our alerting workflows are always working since all the automation can be consolidated into one tool, and I've realized that because employees spend so much time in Slack (especially during incidents), they're more likely to interact with Rootly's features which creates better accuracy in our reporting. For example: if previously an incident was only tracked in a ticket management system which is out of where the team is interacting with the incident -- engineers can sometimes forget to go back into the ticket and resolve the incident or add in resolution notes. That can lead to inconsistencies in MTTR reporting, which ultimately makes it harder to plan and report on. Since Rootly is all in Slack, teams can hit "resolve" or "mitigate" directly from the channel and add in any notes, which I've noticed teams are much more likely to do.
It's made me significantly more comfortable that our alerting workflows are always working since all the automation can be consolidated into one tool, and I've realized that because employees spend so much time in Slack (especially during incidents), they're more likely to interact with Rootly's features which creates better accuracy in our reporting. For example: if previously an incident was only tracked in a ticket management system which is out of where the team is interacting with the incident -- engineers can sometimes forget to go back into the ticket and resolve the incident or add in resolution notes. That can lead to inconsistencies in MTTR reporting, which ultimately makes it harder to plan and report on. Since Rootly is all in Slack, teams can hit "resolve" or "mitigate" directly from the channel and add in any notes, which I've noticed teams are much more likely to do.
Consistent and flexible incident management
What do you like best about the product?
Rootly has helped our team automate a lot of the manual work we were dealing with in our incidents. We had a chance to look at different tools but because we felt our needs were consistently changing ever so slightly, we wanted to find someone we could really partner with for the long term. Rootly has done an impeccable job at listening to our requests, changing needs, and never failed to deliver on something that would help us. Most recently, their custom fields feature was able to help support a new change that was required in our process.
What do you dislike about the product?
This actually wasn’t a dislike for us but It’s worth mentioning. Rootly is bar none the best at adapting their solution to your existing process but it helps if you have something to work with to begin with - even something as simple as a checklist to work from to start.
What problems is the product solving and how is that benefiting you?
Before Rootly, we knew what our process was but it was a lot more tedious to get through and Rootly not only helped build more consistency around it but it eliminated a lot of time wasted. Our resolution time has been ~50% faster. Aside from that, the ease of onboarding new team members became an unexpected benefit.
That is the great incident management tool
What do you like best about the product?
Ease of use, Configurability and flexibility
What do you dislike about the product?
No I have nothing to dislike here. Everything is good.
What problems is the product solving and how is that benefiting you?
We can trigger the incident process quickly via slack, gather the proper team members to solve, and have the appropriate communication across the teams. Every event is tracked and saves a lot of time creating the postmortem.
Recommendations to others considering the product:
If someone ask me about incident tool which I prefer, I will say it is rootly.
Best-in-class for automation and flexibility
What do you like best about the product?
Rootly provides best-in-class automation for manual admin work (e.g. creating Slack channels, tracking action items, postmortem timeline). It seamlessly integrates with our entire ecosystem of tools (Jira, Confluence, OpsGenie, Zoom...) making it very easy for us to plug into our workspace environment and onboard our staff.
Rootly is also extremely flexible. Pretty much everything is configurable! That was one of the decisive factors when assessing multiple vendors: the incident response tool is fitting our internal processes and not the way around. Any changes to our internal response process can be easily & quickly implemented in a couple of clicks. Forget vendor lock-in, use the best tool for each task: postmortem in Confluence or Google Doc, Zoom for the war room... Rootly offers us flexibility unmatched on the market.
Finally, Rootly team is responsive around the clock, any issue is quickly fixed, no question goes unanswered, and are collaborative in brainstorming solutions. Every time that we come up with ideas or feedback from our users, the team helps us to better define our request and come up with an elegant solution to solve our problem, either by leveraging existing features on the platform or by opening a new feature request (which never takes long to get rolled out!). Thanks to the team for listening to us and providing us advice on best practices and delivering improvements on a regular basis! As Site Reliability Engineer in charge of the incident response, there's no better way to start the day than seeing a notification for Rootly latest changelog.
Rootly is also extremely flexible. Pretty much everything is configurable! That was one of the decisive factors when assessing multiple vendors: the incident response tool is fitting our internal processes and not the way around. Any changes to our internal response process can be easily & quickly implemented in a couple of clicks. Forget vendor lock-in, use the best tool for each task: postmortem in Confluence or Google Doc, Zoom for the war room... Rootly offers us flexibility unmatched on the market.
Finally, Rootly team is responsive around the clock, any issue is quickly fixed, no question goes unanswered, and are collaborative in brainstorming solutions. Every time that we come up with ideas or feedback from our users, the team helps us to better define our request and come up with an elegant solution to solve our problem, either by leveraging existing features on the platform or by opening a new feature request (which never takes long to get rolled out!). Thanks to the team for listening to us and providing us advice on best practices and delivering improvements on a regular basis! As Site Reliability Engineer in charge of the incident response, there's no better way to start the day than seeing a notification for Rootly latest changelog.
What do you dislike about the product?
None that I can think of, the product is heading in the right direction and we are pleased to be using Rootly on a daily basis.
What problems is the product solving and how is that benefiting you?
Rootly let us streamline our incident response process. Exit in-house solutions, welcome to the most flexible and open solution on the market, built and ran by a team of world-class experts. Incident Management just got a lot simpler.
For example, our incidents now get immediate attention, the right persons are involved and we are finally able to track and reduce our MTTx metrics.
For example, our incidents now get immediate attention, the right persons are involved and we are finally able to track and reduce our MTTx metrics.
Recommendations to others considering the product:
Take the time to fully explore the product and make the most out of it.
Highly configurable and shipping new feature requests all the time
What do you like best about the product?
Rootly have been a pleasure to partner with since our initial point of contact. They were extremely supportive in our evaluation of the product, as well as throughout the migration from our in-house solution.
Rootly's biggest advantage is probably that the product is highly configurable to fit your incident response process, and integrates with most existing tools. We didn't find this kind of flexibility with many of the other products we evaluated - they often required us to change our processes to fit their product.
We've been using Rootly now for over 6 months, and I've been impressed with their responsiveness to all of our feature requests, often shipping them within a day or two. Whenever there were incidents or questions, we got a response very quickly.
I've already recommended Rootly to another tech company, and they are also having a positive experience.
Rootly's biggest advantage is probably that the product is highly configurable to fit your incident response process, and integrates with most existing tools. We didn't find this kind of flexibility with many of the other products we evaluated - they often required us to change our processes to fit their product.
We've been using Rootly now for over 6 months, and I've been impressed with their responsiveness to all of our feature requests, often shipping them within a day or two. Whenever there were incidents or questions, we got a response very quickly.
I've already recommended Rootly to another tech company, and they are also having a positive experience.
What do you dislike about the product?
There were a few bugs and clunky flows in the early days that needed to be ironed out. That said, Rootly promptly fixed them after being given the feedback.
What problems is the product solving and how is that benefiting you?
Rootly allows our engineers to focus on resolving incidents, rather than battling with tooling/process.
It also means we no longer need to have engineers maintaining an in-house solution - we could never catch up to the number of features Rootly was shipping, and the ongoing operational load was significant.
Rootly has features that support incident response best practices e.g. helping surface incident playbooks.
We're now also moving incident data fields into Rootly instead of wrangling them from Jira, which has always been a huge pain.
It also means we no longer need to have engineers maintaining an in-house solution - we could never catch up to the number of features Rootly was shipping, and the ongoing operational load was significant.
Rootly has features that support incident response best practices e.g. helping surface incident playbooks.
We're now also moving incident data fields into Rootly instead of wrangling them from Jira, which has always been a huge pain.
The team at Rootly really understand incident management
What do you like best about the product?
The slackbot is slick, gives a simple overview to anyone joining and means most users never need to head into the WebUI. This means that users can focus on one communication stream to manage the event, and that stream works for all users (remote and office-based) equally.
What do you dislike about the product?
Not so much a downside, but there are features we don't use (yet) - we have so much alert noise, that we haven't dared to turn on "automatic incident creation". I'd also love to see a management summary that gets sent only to nominated users for the past month.
What problems is the product solving and how is that benefiting you?
We now have clearer ownership of problems that occur. By assigning nominated roles, other "experts" then get out of the way to let those in charge, be in charge. Because of better visibility. we also seeing fewer dragged out incidents, that never progress or close.
Rootly was easiest tool for us to incorporate and implement.
What do you like best about the product?
Very quick and responsive support and seamless integration.
What do you dislike about the product?
Nothing to dislike.. we really love it..
What problems is the product solving and how is that benefiting you?
We could use existing tools in place, e.g. Slack, Jira, PagerDuty, etc. and we love the customizable Workflows to define and set our incident process.
Recommendations to others considering the product:
Using Rootly is a no-brainer if you dont want to complicate Incident Management process.
showing 41 - 50