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.
Firehydrant has a lot of automated features and easily integrate third party apps
What do you like best about the product?
User friendly user interface
It easy to navigate
Can use command to create incident or GUI
It easy to navigate
Can use command to create incident or GUI
What do you dislike about the product?
We should enable copy and paste photo from sniping tool or other tool
What problems is the product solving and how is that benefiting you?
We use it to create ticket instead of our main ticket tool which take a lot of time
using a simple command tickets are created
using a simple command tickets are created
- Leave a Comment |
- Mark review as helpful
Application Support Lead
What do you like best about the product?
All features including screen layout, navigation etc
What do you dislike about the product?
UI is not great, response time on some screens need to be handled
What problems is the product solving and how is that benefiting you?
sometime the configuration are too complex, not that user friendly notations
FireHydrant was rolled out as a central initiative
What do you like best about the product?
The integration with Slack so that notifications can be shared
What do you dislike about the product?
FireHydrant has many different actions and (Slack) commands supported, but it is difficult to understand which ones are relevant to me as a triage engineer, especially since I am typically on call once every three months. One improvement would be to default to a "role based" view that only lists the commands for the user's current role(s) and then perhaps it could be possible to extend that view to include all other commands as well.
What problems is the product solving and how is that benefiting you?
As a triage engineer, my main responsibility during an incident is to bring our services back to normal mode of operations. FireHydrant was chosen as a tool to orchestrate communication during and after the incident.
Good Slack integration - some quirks with the user interface
What do you like best about the product?
Slack integration is a winner. The ability to update the incident using the bot integration and to star comments to add them to the retrospective is a total winner. I've never seen anything like that.
What do you dislike about the product?
The User Interface has some failures. Concurrent editing is not supported, but not blocked either, so it's a dangerous situation. Markdown is avaiable but does not have buttons for it and it's not possible to upload images.
What problems is the product solving and how is that benefiting you?
Incident response and capturing information during the management of an incident in a way that minimizes friction and context switching by staying in the same Slack channel.
Using FireHydrant to review incidents
What do you like best about the product?
What I like the best is the breakdown of important information into different sections for easy readability.
What do you dislike about the product?
What I do not like is that at first it can be difficult to locate the retrospective for an incident.
What problems is the product solving and how is that benefiting you?
A problem FH is solving is a consolidation of all relevant information regarding an incident into one portal. That benefits me by allowing me to review incidents and quickly get an overview of what happened during that incident.
Managing fires made easier
What do you like best about the product?
its slack integration and star emoji helps a lot in tracking an issue's timeline and make those starred messages stand out where they usually would just be buried below all the other non-important messages
What do you dislike about the product?
sometimes I get lost trying to find something specific like the retro but I guess that's because I haven't used it that much as an Incident Owner
What problems is the product solving and how is that benefiting you?
un-organized incident is the problem, and that's something FH is solving for us
FireHydrant is a fundamental piece of my incident management at Twilio
What do you like best about the product?
everything related to the incident is in the same page, so it's easy to find all the related stuff from the incident for traceability
What do you dislike about the product?
the UI on the incident management page sometimes not working as expected. Some fields are a little buggy
What problems is the product solving and how is that benefiting you?
it helps us to coordinate the incident response and get all people related to the incident in touch and updated
It really helps your team to better manage incidents.
What do you like best about the product?
Slack integration, including timeline updates
What do you dislike about the product?
jira integration doesn't include ticket id for new tasks
What problems is the product solving and how is that benefiting you?
Only place for incidents management
Good Incident Management Tool
What do you like best about the product?
Easy to use for someone in a customer-facing role that always needs up-to-date information on incidents to update customers
What do you dislike about the product?
I wish the filter view had the ability for advanced filters through an SQL-like query rather than the basic click-through filtering. Allows you to get more granular when looking for a specific incident that you don't have much info on.
What problems is the product solving and how is that benefiting you?
Great at tracking incidents all the way from reporting to RFO.
Good incident management tool
What do you like best about the product?
I use Firehydrant as a user, not as an administrator. In our product, we allow our users to raise incidents when they find something that is not working as expected. We have it integrated with Pagerduty so depending on incident metadata, an engineer can be paged. It allows us to cover the whole lifecycle of the incident, including post mortem actions, etc. It has excellent integrations with some tools we use.
What do you dislike about the product?
As said before, we have an integration FireHydrant - Pagerduty. In our case, we have found no option to customize the Pagerduty service / escalation policy depending on FireHydrant incident data. This means that for instance, we have been unable to have a different workflow for an incident raised for a Stage environment or a Production issue. This means that sometimes our engineers get paged for Stage environment.
What problems is the product solving and how is that benefiting you?
As explained before, it covers a need that is not covered by our observability tools or Pagerduty, allowing our users to create manual incidents, having the option to track the incident from beginning to end.
showing 11 - 20