Response time and metrics for your API

Every HTTP check records how long your endpoint took, and anything slower than 10s counts as down. Push your own counters and gauges for the numbers a check cannot see: queue depth, database latency, error rate.

Start tracking See the live demo

Works with your stack

logo_NET file_type_rust

Flying Blind on Infrastructure

It's easy to track signups. It's harder to know if your background worker is stuck, or if that new query you wrote is timing out for 5% of users.

When things feel "sluggish", you shouldn't have to guess why. You need raw, technical counters and gauges that tell you exactly which part of your system is sweating.

The backend black box

  • ✕ "Why is the API slow?" becomes a guessing game.
  • ✕ You don't know if your cron jobs actually finished successfully.
  • ✕ You deploy a change and wait for user complaints to know if it broke performance.

The number moves first, the outage follows

Counters and gauges from Node, Python, Ruby, Java, .NET and Go. Measure how long things take and how many things happened, then watch the line bend a day before it takes the service down with it.

Response time recorded on every HTTP check

Your own counters and gauges from six SDKs

Charts that show the slowdown before the outage

Explore other features

Logging

Find the error behind the alert.

Monitoring

HTTP checks and cron heartbeats.