Skip to content

Debugging · Incident review

WhyStack

Reads logs, metrics and traces and tells you what probably caused an incident, using rules you can check instead of a black box.

WhyStack, sketched

Context

The problem

When something's on fire, engineers need an explanation they can verify, not a confident guess.

Approach

How I built it

  1. A rules engine ranks the likely causes using logs, metrics and traces.

  2. Every answer comes with the evidence behind it and a full trail of how it got there.

  3. It's meant to sit next to AI incident tools as the part you can double-check.

Result

What came out of it

  • Likely causes, ranked

  • Evidence for every answer

  • Nothing hidden