FireHydrant
FireHydrantReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
137 reviews
from
External reviews are not included in the AWS star rating for the product.
Blameless helping to improve Space Operations
What do you like best about the product?
The ability to track customer and incident time as separate timespans on the same incident. This allows our team to calculate how long an incident takes to fully resolve when any customer affected services are involved and have been fully addressed.
What do you dislike about the product?
The need to make specific queries and additional calculations to report all associated tags and resolution times for an incident. Currently, the queries automatically multiples the incident time by the number of tags reported. It would be nice if there were easier ways to collect and report this info. Also, the inability to link incidents together for related follow-on incidents.
What problems is the product solving and how is that benefiting you?
It helps our team track incidents and the amount of time our system is affected to ensure we are providing the most up time possible. This is huge benefit to our Customer Success team in quantifying how incidents are affecting our customers.
Unblock your engineers from focusing on incidents
What do you like best about the product?
I love that Blameless allows engineers to focus on whats important, remediating the incident. Integrating within slack allows for engineers to open, document, and resolve incidents from within their standard communcations tool.
With Blameless, Machinify leverages weekly retrospectives to give the broader team awareness in what went wrong throughout the week and how we can avoid it in the future. Reliability insights enables engineering managers to view open incidents, time to resolution and identify patterns within incidents over the past week.
As we continue to rely on Blameless at our organization, engineers continue to focus on excellence when it comes to operating our platform.
Blameless customer support is focused on ensuring all customers are enabled and unblocked throughout their use of the product.
Our organization has over 2000 incidents using Blameless, and we use it every day.
With Blameless, Machinify leverages weekly retrospectives to give the broader team awareness in what went wrong throughout the week and how we can avoid it in the future. Reliability insights enables engineering managers to view open incidents, time to resolution and identify patterns within incidents over the past week.
As we continue to rely on Blameless at our organization, engineers continue to focus on excellence when it comes to operating our platform.
Blameless customer support is focused on ensuring all customers are enabled and unblocked throughout their use of the product.
Our organization has over 2000 incidents using Blameless, and we use it every day.
What do you dislike about the product?
I wish there was more automation around communication, remediation and documentation of incidents within Blameless.
I would love to see more power behind reliability insights and SLOs.
I would love to see more power behind reliability insights and SLOs.
What problems is the product solving and how is that benefiting you?
When I joined my organization, we constantly had incidents that were triaged and resolved in private communcations. This lead to not solving the root problem, reducing transparency in the platform. Blameless improves that transparency, removes toil in the incident process and forces the conversation of root cause analysis.
Flexible Incident Management Tooling
What do you like best about the product?
Blameless automates much of our incident management admin, saving time and improving consistency.
Blameless enables us to track both required and ad-hoc incident management tasks using the same interface.
No lock-in - you can use Blameless for retrospecives and reporting or export your data to another tool.
Excellent onboarding and support.
Blameless enables us to track both required and ad-hoc incident management tasks using the same interface.
No lock-in - you can use Blameless for retrospecives and reporting or export your data to another tool.
Excellent onboarding and support.
What do you dislike about the product?
UX is occasionally unpolished, but is improving.
What problems is the product solving and how is that benefiting you?
Blameless automates common incident management tasks, enabling incident commanders to focus on coordination and resolution.
Good Automation but scope for improvement
What do you like best about the product?
Its automactic tools are superb giving somegood metrics to work upon.
Easy to setup
Easy to setup
What do you dislike about the product?
It needs to understand the market better along with the voice of its customers
What problems is the product solving and how is that benefiting you?
Alert system
Mechamism for our use case
Mechamism for our use case
Rockstars at Incident Management
What do you like best about the product?
The easy to use UI + the simplistic configuration wizards that they have for setting up integrations and to get up and running in commanding your first incidents. The product is straight forward and easy to use and it keeps folks working inside the tools that they are used to using on a day-to-day basis.
What do you dislike about the product?
I wish the UI was a tab bit more polished when comparing to using it via slack but it's nothing that can't be fixed. Just some little browser kinks/bugs here and there.
What problems is the product solving and how is that benefiting you?
Blameless is helping us solve our automated communications problem and informing the teams that need to know about an incident in a quick and easy way. We see alot of productivity to come from Blameless
Blameless easy the implementation of SRE Good Practices
What do you like best about the product?
The slack bot is very intuitive and easy to use. In a few clicks you'll have a ready-to-use step-by-step incident bot. We use it on all incidents!
The incident output is very organized to do post-analysis.
The support is incredible, we have Blameless folks on our slack and they answer any question we have in the same day.
Reliability Insights are very nice for analyzing the company's reliability.
Communications flow can be customized.
The incident output is very organized to do post-analysis.
The support is incredible, we have Blameless folks on our slack and they answer any question we have in the same day.
Reliability Insights are very nice for analyzing the company's reliability.
Communications flow can be customized.
What do you dislike about the product?
Blameless doesn't have integrations to export data to other systems, this force us to do some manual toil to have the data available on other tools, such as Notion.
What problems is the product solving and how is that benefiting you?
It helps us operating incidents in a organized way. This makes us faster, more confident and less error prone during the hardest times.
It helps us organizing the incident data to do post-analysis. This makes us more effective on learning and taking action points to prevent issues from happening again.
It helps us organizing the incident data to do post-analysis. This makes us more effective on learning and taking action points to prevent issues from happening again.
I like firehydrate
What do you like best about the product?
Tracking and conclusion function. It could track the progress of issues. And it is very convenient to write the retro.
What do you dislike about the product?
I like it, really nothing for me to dislike.
What problems is the product solving and how is that benefiting you?
It tracking the progress clearly, so during the triage, you could bring more people anytime and do not need to explain again and again. It saves all records, make it easier for write a retro afterwards.
Effective incident and issue management
What do you like best about the product?
Blameless connects seamlessly with other tools, is fairly robust, customizable, features great reporting, and meets a variety of use cases for our company.
What do you dislike about the product?
Blameless lacks some feature customization paths, but the team is receptive to feedback and regularly rolls out improvements based on feedback.
What problems is the product solving and how is that benefiting you?
Blameless helps our organization effectively manage urgent incidient breaks (app / web / backend service failures) and risk issues (regulatory gaps)
Works brilliantly in our incident management process
What do you like best about the product?
We adopted Blameless to automate and support our incident management process. The tool's Slack-bot is a core feature in managing the process.
At the start of an incident we quickly get an issue ticket, a video chat, and a dedicated incident channel in Slack.
The incident tasks allow the incident to be guided through the process without being heavy handed.
Capturing highlights from the incident channel allows engineers to more quickly prepare for retrospectives.
The insights allow visualisation of almost anything we care to track.
The product has improved consistently since we started using it - and it was more than a solid offering 2-3 years ago.
The support and interaction with the Blameless employees has always been excellent.
At the start of an incident we quickly get an issue ticket, a video chat, and a dedicated incident channel in Slack.
The incident tasks allow the incident to be guided through the process without being heavy handed.
Capturing highlights from the incident channel allows engineers to more quickly prepare for retrospectives.
The insights allow visualisation of almost anything we care to track.
The product has improved consistently since we started using it - and it was more than a solid offering 2-3 years ago.
The support and interaction with the Blameless employees has always been excellent.
What do you dislike about the product?
I consider myself to be a "power user". I quickly bump into the limits of almost any software or system, especially when trying to automate things away. I've struggled in some of these areas, but the (growing) API has already proved useful, as well as some very exciting features expected towards the end of the year.
What problems is the product solving and how is that benefiting you?
Automating and guiding engineers through our incident management process.
Quite helpfull to formatting a postmortem in our usecase
What do you like best about the product?
it boasts a comprehensive task list, streamlining the onboarding process for any new team member. Additionally, it incorporates an extensive "N Why's" template, facilitating the exploration of in-depth causes behind incidents. The inclusion of a comments feature further enhances its utility, particularly during discussions surrounding retrospectives or post-mortems.
What do you dislike about the product?
We've encountered a recurring problem related to accessing retrospectives, which has been duly reported to the blameless team. However, a definitive estimated time of resolution (ETA) for the fix has not been provided. This issue has persisted for a considerable duration and appears to be affecting only certain users.
What problems is the product solving and how is that benefiting you?
Implement a process standardization strategy that encompasses refining postmortem procedures. This involves streamlining formatting and providing clear guidance to engineers, ensuring a unified approach to reporting incidents and comprehending root cause analyses (RCAs).
showing 31 - 40