Plans and limits

Plans #

• Developer — for a single service getting started.
• Pro — for a production team running many services.
• Enterprise — for an organisation with its own governance requirements.

Included #

              Hosts   Seats   Logs       Traces    Metrics
Developer        5      1     7 days     7 days    30 days
Pro            open     10    30 days    15 days   450 days
Enterprise     open    open   365 days   90 days   450 days

Retention is the period each signal is kept and remains queryable. Archived logs are kept in your own storage beyond the live retention shown here.

Pro features #

• Service map, profiling, universal service monitoring.
• Dynamic instrumentation, database monitoring and data streams monitoring.
• Service objectives, scheduled reports and workflow automation.
• Retention filters, notebooks, custom roles and the audit trail.

Enterprise #

Enterprise adds single sign-on, directory synchronisation, bring-your-own storage and an uptime commitment.

Usage #

Usage is counted per organisation and resets each month. The figures on the usage page are the ones your plan is measured against.

• Hosts — machines reporting telemetry.
• Seats — members with access.
• Ingest — volume accepted, measured by signal.

When you reach a limit #

Reaching the ingest limit is visible in the delivery path: requests still succeed and the excess records are dropped with a partial-success notice, so a sender sees warnings rather than errors.

Operating limits #

• A query window may span up to 400 days.
• An ingest request body is limited to 4 MiB.
• The trace list returns up to 500 rows at a time.
• A single trace holds up to 20,000 spans.
• Up to 64 labels per metric series.
• Up to 25 recipients per scheduled report.