I built this to keep track of a worker that was stopping too often without an obvious reason and I had no idea what the job was doing when it stopped. Now, it's been for a few months with very successful results and I decided to make it available to everyone with a nice free tier.
Capto watches heartbeats / cron / HTTP for background jobs, which can carry short breadcrumbs (structured notes, not a log dump). When the ping stops, those last notes are frozen onto the incident and ride along on the alert.
If you'd like to try it out, the link is a live demo on the real API — no account, no email. You get a ping URL for an hour. Curl it a few times, POST a breadcrumb, stop curling, wait. An incident opens with the context still attached.
It's deliberately narrow: not logs, not APM, not on-call. I'd love to get some feedback on it.
I built this to keep track of a worker that was stopping too often without an obvious reason and I had no idea what the job was doing when it stopped. Now, it's been for a few months with very successful results and I decided to make it available to everyone with a nice free tier. Capto watches heartbeats / cron / HTTP for background jobs, which can carry short breadcrumbs (structured notes, not a log dump). When the ping stops, those last notes are frozen onto the incident and ride along on the alert.
If you'd like to try it out, the link is a live demo on the real API — no account, no email. You get a ping URL for an hour. Curl it a few times, POST a breadcrumb, stop curling, wait. An incident opens with the context still attached.
It's deliberately narrow: not logs, not APM, not on-call. I'd love to get some feedback on it.