Pulse docs
Pulse takes OpenTelemetry metrics and logs, keeps them queryable for 7 days, then hands them to your own bucket. It also watches cron jobs and websites. New here? Start with the quickstart.
- Quickstart
- Create an ingest key, point your OpenTelemetry Collector or SDK at Pulse, and see your logs and metrics in Explore.
- Sending OTLP
- The OTLP/HTTP endpoints, ingest keys, formats, compression, size limits, responses, and how metering counts bytes.
- Logs
- How OTLP log records are stored, which fields you can filter on, and how severity and bodies are handled.
- Metrics
- Gauges, sums, histograms and summaries in Pulse: how they're stored and which aggregations work on each.
- Explore and the query API
- Graph metrics and search logs from the last 7 days in Explore, or with POST /api/v1/query.
- Live tail
- Watch logs or metric points arrive in real time, filtered like a query.
- Checks
- Heartbeat checks for cron jobs and scheduled tasks, ping URLs, and HTTP uptime checks.
- Monitors
- Alert when a metric or a count of matching logs crosses a threshold for a while.
- Alerts and Shift
- Where check, monitor and archive alerts go: Shift Events v2 with a routing key, or email to org admins.
- Archive and grace hold
- How Pulse hands your data to your own bucket on day 7, the file layout and manifest, and what happens when the bucket isn't reachable.
- MCP
- Connect Claude or any MCP client to Pulse with an API key or OAuth, and the tools it gets.
- REST API
- Authentication, scopes, conventions and every /api/v1 endpoint.
- Limits
- Request sizes, retention, query caps and other limits during the beta.
- Security
- Where your telemetry lives, how keys and ping URLs work, who can do what, and what Pulse keeps.
Every page is also plain Markdown (add .md to its URL), and /llms.txt lists them for AI assistants.