It’s been a minute since I wrote a technical blog post about FireHydrant, but I think I’m making up for it with this doozie. Check out how we structure our integration architecture in a way that’s allowed us to release a new integration every month for the past three years.
With the other competitors I get the point of targeting smaller customers. With that said, I think a point might be missed with what I'm trying to accomplish with this initially: Context being lost through engineers finding things. Metrics, logs, traces, etc all don't tell a root cause when its a new incident. That's usually a human putting 2 and 2 together. When that happens it can be lost never to be seen again (the trail of tears getting to the solution).
This is a super early release and this feedback was invaluable so thank you very much! There are plenty of ideas I'll be implementing in the coming weeks now that this first release is finally out of the way.