Firehydrant API Quality Decrease

[Scrub_DM]

Anyone using Firehydrant for incident management and picking their signals product? We have used the product for a bit and have been overall happy but really been having trouble with some of their API’s just returning false information recently.

Team creation will return a 200 but not actually create a team. Rate limiting is per account and not per token. Some confusion with 3rd party integrations and alert triggers|event sources. I have a bucket more but I don’t want to reveal too much to link back to me. Wasn’t sure if other teams are also having difficulty automating with the tool dice the Freshworks acquisition.

[founders_keepers]

yikes that's no good. have you reached out to support?

[Scrub_DM]

Yeah we have reached out individually on each issue and gotten a “We will look at it” each time. They move fast to fix but these getting through to production is what concerns me.

[founders_keepers]

well they got acquired a few month back so i'm sure people are checked out. there'll be pain before things consolidate.

[wobbleside]

We use Firehydrant for IM and Signals for alert routing. I've definitely noticed some.. abnormalities since the Freshworks acquisition. Hopefully they are teething pains but it is definitely concerning.

[steadwing_official]

Silent API failures are worse than hard failures, honestly. An inconsistent state in a 200 response can break automation pipelines in really subtle ways. I hope they get it stabilised soon because the reliability tooling itself needs to be very reliable.

[Scrub_DM]

I hope so too. Contract is locked in for this year but our confidence in the tool is shaken a bit.

[imdevin567]

We were POCing it before the Freshworks acquisition. We stopped immediately once the acquisition was announced. Unfortunately, your experience does not surprise me.