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.
Incident management using Rootly
What do you like best about the product?
Easy to use, Configurable, Automation. nothing else
What do you dislike about the product?
Coaching people to use it, nothing else t
What problems is the product solving and how is that benefiting you?
The biggest problem that Rootly resolved for us is automating communications during the life cycle of an incident. When our engineers are busy trying to resolve an incident it is difficult to remember to communicate the status of the incident and update the appropriate teams when the status has changed. Rootly has provided us with easy-to-use automation that does this for us. Since onboarding Rootly we have had seamless communications around the lifecycle of an incident allowing our account executives, support engineers, and customers to rest assured that their interruption in service is being prioritized. Rootly is highly flexible and configurable to fit our process and we did not have to change our process to fit Rootly functionality. Their support team responds very quickly any time we have a question and we are able to input improvement ideas to them and are confident that those ideas have a solution quickly.
- Leave a Comment |
- Mark review as helpful
Rootly - A Great Journey so far.
What do you like best about the product?
Using the Web UI of this tool is very easy to use.
Also, we love the fact that this tool integrates easily with other tools such as Slack(for example) especially since we utilize a lot of the tools that can also integrate with Rootly to make our day-to-day operations go a lot smoother. Also, it helps that we can use this tool as almost the central command center for all of the other tools that we utilize in our organization.
Also, we love the fact that this tool integrates easily with other tools such as Slack(for example) especially since we utilize a lot of the tools that can also integrate with Rootly to make our day-to-day operations go a lot smoother. Also, it helps that we can use this tool as almost the central command center for all of the other tools that we utilize in our organization.
What do you dislike about the product?
Currently, configuring this tool as code with Terraform is a challenge. There isn't an easy way to find the correlation between the teams/services/workflows that they utilize. This aspect can frustrate engineers to where it may be better to configure a team's alert/incident workflow configuration via the Web UI.
What problems is the product solving and how is that benefiting you?
It's easier to gather the correct folks for an incident that was triggered and to keep records of the important things discussed in the incident and store the information needed via Rootly tool itself.
A powerful Slack-based Incident Management tool
What do you like best about the product?
The flexibility of Rootly's workflows has allowed us to create a handful of solutions for problems that are unique to our company. We have been able to use Rootly to design solutions that fit the needs of our internal teams, reducing cognitive overhead and increasing consistency in how we manage incidents. The number of integrations that Rootly provides with other software vendors increases every week, and this helps to create automation around tasks we perform during incidents.
What do you dislike about the product?
Many of the user interfaces within the Rootly web admin are overwhelming and confusing. I do hope that the Rootly product will improve its UIs over time, with more consistency and usability.
What problems is the product solving and how is that benefiting you?
Rootly is constantly adding new features and integrations to their product and they do so with blazing speed. The Rootly team is very receptive to feedback and suggestions and they have been very responsive to our inquiries when needed.
Customer focused is an understatement.
What do you like best about the product?
Rootly has delivered feature requests when others have ignored us due to our small footprint. During our original POC we were unable to use all of Rootly's features due to our Slack account level of Business+Plus. Even though we are not a large customer Rootly worked with us and resolved the issue. Direct communication between Rootly and our team has made setup a breeze.
What do you dislike about the product?
Rootly solves our problems and we have no real cons when using the platform.
What problems is the product solving and how is that benefiting you?
Automating Slack channel creation as well as tagging stakeholders will save time when it matters most. Previously we have done this manually which usually causes someone to be left out of the loop. Alternatives to Rootly seem to always lack some feature or intergation we require. Rootly has every thing we need in one platform.
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.
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.
showing 31 - 40