Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
135 reviews
from
External reviews are not included in the AWS star rating for the product.
Great Incident Management Software
What do you like best about the product?
Blameless is really easy to configure and navigate once you get familliar with the tools they offer. Comms Flow is a nice a feature that allows some great automation of messages and notifications to be sent out during various stages of the incident. Their support has also been very quick and friendly with anything I've needed. Definitely a tool I use everyday so I've been pleased with the support and ease of use.
What do you dislike about the product?
If you're new to incident management, understanding the methodology behind it can take a minute to get used to before you're really leveraging the full power of Blameless, but their support team is super helpful in bringing you up to speed. If you're familiar with incident management, it's a breeze to get acquainted with.
What problems is the product solving and how is that benefiting you?
Quick Incident identification and bringing in the right people to triage. Being able to require specific frameworks with how incidents are run and how retrospectives should be defined is incredibly useful, gives out a lot of good metrics to work with from a reporting standpoint.
FireHydrant has been a key part of our incident maturation process
What do you like best about the product?
FireHydrant offers a tremendous amount of flexibility for incident automation and visibility. We've had a seamless transition onto the platform and responsive support when small quirks emerged.
FireHydrant has been effectively adopted by the entire engineering org, and initial internal satisfaction has been high.
There are a ton of additional incident process and platform improvements that previously felt pie in the sky, but FireHydrant's flexible runbooks, integrations and webhook capabilities make them actionable to us.
FireHydrant has been effectively adopted by the entire engineering org, and initial internal satisfaction has been high.
There are a ton of additional incident process and platform improvements that previously felt pie in the sky, but FireHydrant's flexible runbooks, integrations and webhook capabilities make them actionable to us.
What do you dislike about the product?
We are still figuring out how to map many discrete systems in our technology stack to the right unlocks in FireHydrant. This includes things like how to keep the catalogs and teams fresh. Thus far, hasn't been a major pain point though.
What problems is the product solving and how is that benefiting you?
We use FireHydrant for incident coordination and analytics.
Blameless is an integral part of Leolabs incident management
What do you like best about the product?
The slack integration is particularly solid, enjoy the fact that I dont need to leave slack to complete an incident end to end.
What do you dislike about the product?
The inbuilt reliability insights are clunky and less than useful. Actually easier to export all incident data using the API and manipulate in a third party tool. Slack integration is great however it would be even better if more functions were integrated. Completion of retrospectives in slack would be excellent
What problems is the product solving and how is that benefiting you?
Leolabs has a need to coordinate incident management across multiple sites and timezones and blameless makes it easy to ensure that all this communication is occurring in one place
Great company with a great product!
What do you like best about the product?
FireHydrant teams listens to feedback and makes lots of improvements to their products via feature requests. Their customer support responds quite quickly.
What do you dislike about the product?
Sometimes you need to use workarounds to make certain integrations work.
What problems is the product solving and how is that benefiting you?
When an issue arises, being able to have everyone on the same tool, following the same process in a standardized way. Having integrations with Zoom and Slack and the ability to kick off an incident very quickly to investigate allows us to focus on mitigation.
Blameless is the engine that runs our Incident Program.
What do you like best about the product?
Blameless helped us establish the framework for our Incident Program. Everything runs through Blameless, from starting incidents to running our retrospectives and collecting incident metrics. Our Blameless CSM Matthew is also excellent. He has been with us since the beginning and has done everything possible to assist and help us.
What do you dislike about the product?
A few functionalities are a total head-scratcher and sometimes work against us. The good news is that Blameless is always committed to take these to their backlog and worked on them. Since our time with Blameless, I have seen some functionality be improved based on feedback, so there is hope.
What problems is the product solving and how is that benefiting you?
Blameless is the framework for which we launch our incident command. It also acts as our de facto data collection for our incident metrics and integration into all our tools.
Reliable Incident Response Product
What do you like best about the product?
It streamlines the Incident response process by automating cumbersome tasks like creating a slack channel, audio bridge, and adding responders to a triage. It is also easily integrated.
What do you dislike about the product?
No downside. Maybe some features regarding stakeholder communications would be a possible enhancement
What problems is the product solving and how is that benefiting you?
Its used as our main incident response tool. It enables the team to focus on driving incidents rather than going through mundane manual processes of creating channels and audio bridges. More attention can be paid to the task at hand
Managing Incidents with Blameless
What do you like best about the product?
Blameless allows us to manage incidents with ease. The integrations with slack and PagerDuty drives quick notifications to the broader team which has significantly reduced our time to identify and time to resolution.
Our newest Customer Support Manager has been great! In her first week, she was able to correct the issues we were facing with the UI and has provided solid communication as we work together to identify how Blameless can help us achieve our 2024 goals.
Our newest Customer Support Manager has been great! In her first week, she was able to correct the issues we were facing with the UI and has provided solid communication as we work together to identify how Blameless can help us achieve our 2024 goals.
What do you dislike about the product?
Blameless continues to release additional features that improves the experience for us as a user/incident manager. Minor changes have impacted our experience - not being able to use capital letters in our tagging. The Blameless team has been open to our feedback and works to make the necessary changes.
What problems is the product solving and how is that benefiting you?
We use Blameless as a mechanism to report, manage, and resolve client impacting incidents. Consistently entering tickets to report incidents has allowed us to measure the time it takes to identify the issue and the time it takes to provide resolution. Leveraging the tags in Blameless helped us identify a pattern of incidents post new release and enabled us to track specific product issues.
Great service for incident&problem management
What do you like best about the product?
-Runbook automation
-UI is easy to use
-Number of features
-UI is easy to use
-Number of features
What do you dislike about the product?
Analytics can be improved. However, new features are being added consistently.
What problems is the product solving and how is that benefiting you?
Saves time on MTTR
The best solution for incident management software
What do you like best about the product?
Very easy to use, works natively with Slack/Teams, and many other integrations.
Very customizable and can be easily tailored to each company's specific needs
Very easy and straightforward implementation process
Customer Support/Account Managers are top notch, and the company as a whole is "client friendly" and open to suggestions/improvements.
Very customizable and can be easily tailored to each company's specific needs
Very easy and straightforward implementation process
Customer Support/Account Managers are top notch, and the company as a whole is "client friendly" and open to suggestions/improvements.
What do you dislike about the product?
To get the best out of the tool you'll need to purchase seats for every user who interacts with incident management
What problems is the product solving and how is that benefiting you?
Coordinating and communicating during incidents, controlling the flow of information during incidents, and ensuring that the right people are working on solving the problem. FireHydrant does all of that while using existing tools (Slack/Teams, OpsGenie/Page Duty) but augmenting them in a way that helps the organization better control and coordinate incidents. This has enabled us to improve "time to resolution," improve efficiency in incidents and reduce burnout of people involved in incidents.
Minimizes Stress, Maximizes Productivity
What do you like best about the product?
Firehydrant has filled nearly every cap that we experienced in the past with incident management. From day one transitioning to FireHydrant, they have proved to be a great investment and improvement over our previous product. Firehydrant has freed my team to spend time on improving processes rather than fighting the incident process itself.
What do you dislike about the product?
I wish Firehydrant had a better maintnenace product. We have not moved our organization to Firehydrant for our maintenances because there is no way to plan and dicscuss in a dedicated channel prior to the start of the maintenance. This makes planning for such events much more difficult to the point where we still use an in-house built tool to run our maintnance.
What problems is the product solving and how is that benefiting you?
Before FireHydrant we were using a house-built tool. Since implementing the product, I have been able to focus more on our processes rather than bug squashing or feature requests. Our incident processes have improved immensly as an organization now that we can focus on the important tasks.
showing 11 - 20