Repository navigation
Relia: Koa request tracing that explains what broke in plain words #2038
virajrakholiya
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm building Relia, a monitoring tool for small teams without an SRE. I'm sharing how it works with Koa, since Koa apps often run with very little monitoring.
Setup
The CLI detects a Koa API, generates the tracing file and loads it before your app. Once that's done, each request is traced: route, status, latency, errors, plus the outgoing HTTP calls it makes.
What it does with that
Most tools stop at collecting traces. Relia learns a baseline for each route. When something drifts (a slower route, a new error, a dependency timing out), it says in plain words what broke, who it hit and where to look. It suggests fixes and never edits your code.
There's a demo that needs no signup: https://app.tryrelia.com/demo?utm_source=github&utm_campaign=lead-agent
Feedback I'd find useful from Koa users: do you put error handling in one top-level middleware, or spread it across routes? That decides whether Relia should report the error where it's thrown or where it's caught.
All reactions