We’re helping teams do root cause analysis with Prometheus

Hacker News

Share card

We’re helping teams do root cause analysis with Prometheus

Hey HN, I’m Matt and I’m on the founding team at https://www.asserts.ai We help teams use their Prometheus metrics to solve problems faster and remove the toil from their troubleshooting workflows. Everyone already uses dashboards and alerts, but these don’t scale well. Why not? The usual advice is to alert on symptoms but then you have to hunt for the cause of the problem by either sorting through lots of dashboards or writing PromQL queries. That gets tiresome when you’ve got a busy on-call rotation or a complex app. Here’s what we do: you send us your Prometheus metrics and we scan them to build a map of your app and infrastructure. We continuously check your metrics for common problems like resource saturation, error spikes, and so forth (we have a library of health checks but you can write your own too in PromQL.) You also set up some service level objectives so we know what’s important to you. When something goes wrong, we show you both the symptoms of the problem and all the potential causes we detected on a timeline so you can easily connect the symptom to the cause. To try us out, you set up a remote write of your metric data from your Prometheus to our hosted storage. This usually takes just a few lines of configuration and 5 minutes. Are you happy with your team’s troubleshooting workflow? Your feedback and thoughts would be really helpful!