# Pulse

> Pulse takes OpenTelemetry metrics and logs over OTLP/HTTP (POST /v1/metrics and /v1/logs, protobuf or JSON, gzip welcome) for $0.10 per GB, keeps them queryable for 7 days (Explore, a query API, live tail), and on day 7 hands the data to your own S3, R2 or GCS bucket as Parquet files with a manifest. It also runs heartbeat checks for cron jobs and HTTP uptime checks, and monitors on metric and log queries; alerts go to Shift (Events v2) or by email to org admins. Everything is reachable over a REST API and an MCP server. Traces are not accepted yet. Invite-only beta.

## Docs

- [Quickstart](https://pulse.nightroll.app/docs/quickstart.md): Create an ingest key, point your OpenTelemetry Collector or SDK at Pulse, and see your logs and metrics in Explore.
- [Sending OTLP](https://pulse.nightroll.app/docs/otlp-ingest.md): The OTLP/HTTP endpoints, ingest keys, formats, compression, size limits, responses, and how metering counts bytes.
- [Logs](https://pulse.nightroll.app/docs/logs.md): How OTLP log records are stored, which fields you can filter on, and how severity and bodies are handled.
- [Metrics](https://pulse.nightroll.app/docs/metrics.md): Gauges, sums, histograms and summaries in Pulse: how they're stored and which aggregations work on each.
- [Explore and the query API](https://pulse.nightroll.app/docs/explore-and-query-api.md): Graph metrics and search logs from the last 7 days in Explore, or with POST /api/v1/query.
- [Live tail](https://pulse.nightroll.app/docs/live-tail.md): Watch logs or metric points arrive in real time, filtered like a query.
- [Checks](https://pulse.nightroll.app/docs/checks.md): Heartbeat checks for cron jobs and scheduled tasks, ping URLs, and HTTP uptime checks.
- [Monitors](https://pulse.nightroll.app/docs/monitors.md): Alert when a metric or a count of matching logs crosses a threshold for a while.
- [Alerts and Shift](https://pulse.nightroll.app/docs/alerts-and-shift.md): Where check, monitor and archive alerts go: Shift Events v2 with a routing key, or email to org admins.
- [Archive and grace hold](https://pulse.nightroll.app/docs/archive-and-grace.md): 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](https://pulse.nightroll.app/docs/mcp.md): Connect Claude or any MCP client to Pulse with an API key or OAuth, and the tools it gets.
- [REST API](https://pulse.nightroll.app/docs/api.md): Authentication, scopes, conventions and every /api/v1 endpoint.
- [Limits](https://pulse.nightroll.app/docs/limits.md): Request sizes, retention, query caps and other limits during the beta.
- [Security](https://pulse.nightroll.app/docs/security.md): Where your telemetry lives, how keys and ping URLs work, who can do what, and what Pulse keeps.

## More

- [Everything in one file](https://pulse.nightroll.app/llms-full.txt): all docs pages, concatenated.
- [AI & MCP](https://pulse.nightroll.app/ai): the MCP server URL and how to connect.
- [Pricing](https://pulse.nightroll.app/pricing): meters and prices.