Real-time API observability

See every request
the instant it slows down.

Pulsegrid streams latency, throughput and error rates from every service as they happen. When a metric crosses its SLO, the timeline lights red and on-call gets paged — not five minutes after your users do.

Start free — 14 days See it live ↓ No agent. Drops in via OpenTelemetry.
production · us-east-1 · services overview LIVE
SLO: p99 latency < 180 ms  ·  demo runs on synthetic data
p99 latency within SLO approaching breach → paged
Why we built it

It's 03:14. Checkout p99 has been climbing for nine minutes. Retries pile up, the queue backs into payments, and the first thing anyone hears about it is a customer tweet.

By the time someone opens a dashboard, greps the logs and finds the one deploy that did it, the incident is twenty minutes old.

Pulsegrid collapses that window. Every request is measured as it lands, every service has an SLO, and the moment a line crosses it the timeline reacts — breach detected → context attached → on-call paged — in under ten seconds.

Monitoring

Live metrics, not five-minute-old graphs.

Latency, throughput, error rate and saturation stream in per service at one-second resolution. Percentiles are computed on ingest, so p99 is honest — no averaging that hides the tail.

  • p
    True percentiles

    p50 / p95 / p99 / p99.9 from raw histograms, per route and per version.

  • Sub-second streaming

    Charts flow in real time over WebSocket — pan back through 30 days without re-querying.

  • Deploy overlays

    Every release marks the timeline, so a regression points straight at the commit that shipped it.

checkout-api · p99 latency · last 60s
p50
p99
throughput
Alerting

Get paged for the breach, not the noise.

Define an SLO once. Pulsegrid watches the burn rate, suppresses flapping, groups related signals into a single incident, and routes it to the right on-call by severity.

  • Burn-rate alerts

    Multi-window SLO burn detection — page fast on a hard breach, ticket slowly on a slow leak.

  • Smart routing

    Critical wakes on-call; warnings open a Slack thread; info files a ticket. All from one policy.

  • Auto-grouping

    Correlated spikes across services fold into one incident with a shared timeline — no alert storm.

CRITICALp99 > SLO for 2mcheckout-api→ PagerDuty
CRITICALerror rate > 5%payments→ On-call phone
WARNINGp95 approaching SLOsearch→ #incidents
WARNINGsaturation > 80%event-bus→ #platform
INFOdeploy shippedapi-gateway v2.14→ Timeline
Integrations

Drops into the stack you already run.

Ingest over OpenTelemetry, ship alerts everywhere your team already lives. No proprietary agent, no rip-and-replace.

OpenTelemetrynative ingest
Kubernetesauto-discovery
AWS Lambdacold-start aware
PostgreSQLquery traces
Kafkalag & throughput
PagerDutyon-call routing
Slackincident threads
GitHubdeploy markers
By the numbers

Built to catch it before you do.

The numbers our own platform holds itself to — measured on the same engine we sell.

0s
Median detect-to-page
breach → on-call notified
0%
Ingest pipeline uptime
trailing 12 months
0B
Spans ingested / day
across all customers
0s
Chart resolution
no rollup smoothing
Who it's for

One signal source, every on-call.

On-call engineer

Wake up to context, not a mystery.

The page arrives with the breaching service, the deploy that caused it and the last 30 minutes of every correlated metric already attached.

SRE / Platform

SLOs that mean something.

Set error budgets per service, watch burn rate in real time, and let routing policy decide who gets woken — codified, not tribal.

Eng leadership

Reliability you can report on.

Weekly SLO attainment, MTTR trends and incident retros roll up automatically. No spreadsheet archaeology before the review.

“We cut mean-time-to-detect from eleven minutes to under ten seconds. Half our Sev-1s now close before the status page would have gone yellow.”
— Priya N., Staff SRE · Meridian Payments
Northwind Vellum Orbital Kettle&Co Meridian Fathom
Start free

Point it at one service. Watch the tail light up.

Fourteen days, full platform, no credit card. Ship an OTel exporter and you're live in minutes.

✓ Workspace provisioning — check your inbox for the OTel endpoint.

Prefer to read first? See how this page was built.