Telemetry billing and retention
Independent signal plans
Section titled “Independent signal plans”Logs and traces each have their own pack. One signal exhausting its allowance does not consume or stop another signal. A GB means 1,000,000,000 bytes. There is no pooled telemetry pack, per-seat telemetry charge or automatic overage billing.
| Logs or traces, each | Monthly price | Retention |
|---|---|---|
| 5 GB | Free | 7 days |
| 50 GB | $15 | 30 days |
| 250 GB | $60 | 30 days |
| 1,000 GB | $200 | 30 days |
Bytes describe accepted customer data before transport compression, using the accepted OTLP protobuf encoded representation for OTLP, original UTF-8 record bytes for custom JSON/text and the adapter’s decoded-record representation for platform payloads. Internal copies, storage compression and replication do not increase billed ingest. Rejected records and data excluded by customer rules do not consume accepted ingest bytes. Processed input still has a separate abuse ceiling, so exclusions do not authorize unbounded free processing.
Metric series
Section titled “Metric series”| Average active hourly series | Monthly price |
|---|---|
| 2,000 | Free |
| 10,000 | $25 |
| 50,000 | $100 |
| 200,000 | $350 |
An active series is a distinct metric identity with its resource/point label combination observed during an hour. Distinct counts for each hour are averaged over the billing month. It is not a count of samples, events, unique label values or the largest daily peak. Sending a point every second instead of every minute does not create a new series if its identity stays the same. A user ID, request ID or changing URL in a label can create many series. Keep those in logs or traces instead.
The Metrics cardinality view shows active series and expensive labels. Account and per-metric cardinality limits can reject new series while continuing known series. Inspect metric partial-success reasons and Usage before increasing cardinality.
Metric retention
Section titled “Metric retention”| Representation | Free | Paid metrics pack |
|---|---|---|
| Raw points/distributions | 7 days | 15 days |
| Minute rollups | 45 days | 45 days |
| Hour rollups | 30 days | 395 days |
A rollup is an aggregate, not an archived raw event. Query responses identify source, precision and quality. Retention can remove raw detail, exact recomputation inputs and exemplar targets while a longer-lived chart remains. Do not infer zero when a bucket is missing. Logs and traces do not inherit metric rollup retention.
Limits and notifications
Section titled “Limits and notifications”Usage emails are sent at 80%, 100% and 110%. The 10% grace buffer ends at the hard 110% boundary, where the affected signal receives 429 with Retry-After. Rate limits, processed-input ceilings and cardinality guards can refuse requests before a monthly allowance is exhausted. Queue data locally and honor retry guidance; upgrade deliberately rather than assuming overflow will be stored or billed.
There is no automatic overage billing and no separate spending cap. Telemetry packs cost the same per month on monthly or annual billing; annual billing has no discount. Accounts with early access can buy paid packs in Account billing; other accounts get an error asking them to contact support. RUM, replay, monitors, status pages and incident pricing remain separate.