Ask HN: Built API monitor with root cause analysis – unable to find first users

Re:Ask HN: Built API monitor with root cause analysis – unab... by theamk on Thursday March 12, 2026 @12:30AM (#47346458)

"Root cause analysis" is pretty complex, and DNS + TCP + TLS are just a tiny bits of it (and they are one of the most reliable ones too, as those components are written once and then typically never touched).

When I do root analysis, I look into internal logs, server metrics, recent source code changes, and related systems. I am sure this can be partially automated, but this is a lot of work.

An API monitor that can only tell me "You have elevated first-byte latency and increased 5xx rate" is pretty useless, and I certainly don't think it can offer me any "plain-english suggestion" for this problem. What is it going to tell me, "git gud and fix your servers"?

[ Parent | on HN ]

Re:Ask HN: Built API monitor with root cause analysis – unab... by acrtic on Thursday March 12, 2026 @12:47AM (#47346566)

Thanks for your insight, Is there something i could implement to possibly make this stand out? Ive got around 60 visits over the past 5 days but only 1 user registered and actually tried it out. What am i missing?

[ Parent | on HN ]