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.
Easy to use, responsive team
What do you like best about the product?
Rootly integrates very well with Slack and makes it easy to keep incidents up to date. Questions and feedback are addressed promptly by the team!
What do you dislike about the product?
We've had very few issues with the platform, and the Rootly team has been very responsive to any issues we've encountered.
What problems is the product solving and how is that benefiting you?
Incident management is made easier -- Rootly adds guiderails to make sure important information isn't missed.
- Leave a Comment |
- Mark review as helpful
GlossGenius <> Rootly
What do you like best about the product?
Rootly creates a clear flow for creating, running, and reflecting on incidents. It incorporates all of our existing tools (Slack, PagerDuty, Google teams, notion, etc) allowing us to work where we want and how we want.
What do you dislike about the product?
Rootly is building super fast, which is awesome! They're experimenting and still figuring things out, as a result, the web app can at times feel overwhelming and a little disorganized. This is expected at this stage as product velocity trumps information hierarchy. I am confident that this will get better over time.
What problems is the product solving and how is that benefiting you?
Consistent and predictable incident management.
Rootly automates a sometimes chaotic incident process
What do you like best about the product?
The opening moments of an incident are a bit panic-inducing. Rootly's automations and Slack integrations cut through the noise to notify the right people, prompting for updates or internal and external messaging. It is incredibly flexible, and it's possible to create custom configurations, messages, custom post mortem documents with links to Jira tickets. Rootly "magically" pushes Slack comments, graphs, code snippets, etc. into the incident timeline on the incident webpage AND into the post-mortem document -- the amount of work saved on that alone is huge!
The team has been amazing to work with -- listening to us and implementing suggestions, or requests for improvements. In circumstances where something needed to be put into their backlog, a workaround or alternative was provided. Their team is incredibly responsive and has been great to work with.
The team has been amazing to work with -- listening to us and implementing suggestions, or requests for improvements. In circumstances where something needed to be put into their backlog, a workaround or alternative was provided. Their team is incredibly responsive and has been great to work with.
What do you dislike about the product?
We have a couple of outstanding requests (on their backlog) for more granular control in configurations, especially on triggers for things happening, and on timing of notification in which channels.
What problems is the product solving and how is that benefiting you?
While we had an incident process that was working, automating it summons the right people to the room to quickly investigate and resolve issues. Their metrics in setting SLOs and site functionality gives us insight into our more fragile areas.
Seamless incident management with a wide variety of integrations
What do you like best about the product?
Central dashboard UI for reporting, complete incident management from within Slack, integrations with bug tracking tools, excellent support team
What do you dislike about the product?
We found some minor bugs but the team at Rootly fixed those quickly
What problems is the product solving and how is that benefiting you?
We've now collated our incident response playbooks and workflows into one place that's easy to use, and it gives us consistent reporting across departments
Rootly is easy to use, deploy and manage
What do you like best about the product?
The automation and integration features are the best part of the solution. Rootly is also easy to use both as an administrator and an incident reporter. The touchpoints to commonly used tools like Slack, Asana, Zoom and PagerDuty are easily enabled or modified as needed. We could start with the more basic functions, deploy to a few departments and continue to iterate and add functionality without business disruption.
The expectation is that Rootly is a tool that can grow with us over time and the Rootly team has been a great partner. They seek recommendations for improvements regularly. When a new feature is requested from our users, we can quickly provide this input to the team. They ask thoughtful questions and provide recommendations for improvements. And then, they quickly deliver.
The expectation is that Rootly is a tool that can grow with us over time and the Rootly team has been a great partner. They seek recommendations for improvements regularly. When a new feature is requested from our users, we can quickly provide this input to the team. They ask thoughtful questions and provide recommendations for improvements. And then, they quickly deliver.
What do you dislike about the product?
An area where Rootly could improve is in the features that assist the post-incident review process. Once an incident is closed, Rootly can auto-create a customized post-mortem template. However, the hand-off to the post-incident is one-directional. It would be great to see Rootly extend its automation features to the post-incident processes where the participants of the incident are also assigned roles to make sure that the root causes, impact-analysis and key actions are tracked and completed.
What problems is the product solving and how is that benefiting you?
There were three key focus areas that were driving the requirements for deploying an incident management tool: automation, standardization and metrics. Rootly has provided us immediate results with all three. We will continue to grow the process and expect that Rootly will be a great tool to continue to build on.
Recommendations to others considering the product:
Contact Rootly and let them know what your goals are. The team is very collaborative and you can bring up your own specific requirements and they will work with you.
Slack native and enterprise ready
What do you like best about the product?
Having worked with old school incident management platforms, Rootly is a breath of fresh air.
Our team was already using Slack to manage incidents and so I wanted a tool that would complement our flow and not displace it with a different tool. Rootly hit the brief almost perfectly. In the few areas where we saw gaps, the team has always been super responsive in addressing them. More than once, a feature request was implemented within a couple of days! The team genuinely cares about their customers - even the small ones who are halfway around the world!
Our team was already using Slack to manage incidents and so I wanted a tool that would complement our flow and not displace it with a different tool. Rootly hit the brief almost perfectly. In the few areas where we saw gaps, the team has always been super responsive in addressing them. More than once, a feature request was implemented within a couple of days! The team genuinely cares about their customers - even the small ones who are halfway around the world!
What do you dislike about the product?
Most things which we didn't like, the team at Rootly has been proactive in fixing them. The next area of improvement I'm waiting on (and is in their roadmap) is improvements to their support for config-as-code. With the number of workflows that we have created now, I'd love to start using Terraform to manage Rootly configs.
What problems is the product solving and how is that benefiting you?
We use it to manage our high severity incidents as well as to retain an audit of activities during an incident to aid post-mortems. We have also started using the status pages internally.
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.
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.
showing 31 - 40