pulse1import { pulse } from 'pulse-agent';23pulse.init({4 cluster: "prod-us-east",5 sampleRate: 1.0,6 alerting: true,7});
Three lines. Full observability.
Drop the agent. Watch every server heartbeat, API response, and memory spike across your entire Kubernetes fleet — before your users feel a thing.
73% of outages are detected after user impact.
By the time your on-call engineer gets paged, the damage is already measured in lost transactions and SLA violations. Pulse fires alerts the moment a metric crosses threshold — not after a 5-minute polling cycle.
↑ Drag the slider to adjust the threshold and watch alerts fire
MTTR drops 41% with correlated traces.
When your payment service slows, is it the database, the network, or the upstream SDK? Pulse stitches every span into a single causal trace — click any service, see the exact bottleneck in milliseconds.
← Click any span in the trace to expand its attributes
Every signal. One pane.
Install the Agent.
Start seeing everything.
One command. Auto-discovers your services, instruments your code, and starts streaming metrics in under 90 seconds.
$ curl -sSL https://get.pulse.sh | bash -s -- --cluster prod-us-east
From the engineers who run it at 2 a.m.
We had a memory leak in our Rust service that took 3 days to find with our old stack. Pulse correlated the trace in 11 seconds. Literally 11 seconds.
Our enterprise clients need proof of four-nines. Before Pulse, that meant a painful export every quarter. Now I share a live dashboard URL and it's done.
2 a.m. Kubernetes incident. Three time zones of engineers. Pulse's correlated alerts meant we had root cause before the incident bridge even fully assembled.
Your cluster is already talking.
Pulse listens. Drop the agent and get full observability in under 90 seconds — no YAML archaeology required.