Skip to content
Maple Docs
Open app
Browse the docs
On this page

Retention

How long hosted Maple keeps each kind of data: traces, logs, metrics, session replays, product events, error issues, alert history and the audit log.

Hosted Maple deletes data automatically once it passes its retention period. The periods are the same in both regions. Age is measured from the data’s own timestamp (for example a span’s start time), not from when Maple received it.

Telemetry

DataKept for
Traces (spans)30 days
Logs30 days
Metrics (sum, gauge, histogram, exponential histogram)90 days
Session replays (recordings and their timeline events)30 days
Product events365 days
Error occurrences (the individual events behind error issues)90 days
Hourly rollups of traces and logs (service overview, service map edges, trace and log aggregates)365 days

Individual spans, log lines and data points cannot be read once they pass these periods. Charts built on hourly rollups, such as service overviews and the service map, can reach further back, up to the rollup’s 365 days. Some queries have shorter maximum time ranges. See Limits.

Error issues

Error issues are not deleted by age while they are open, however old the underlying errors are. These rules clean them up:

Issue stateWhat happens
Resolved (done) for 14 daysThe issue is archived
Grouped under an older fingerprinting scheme, after Maple changes how errors are groupedThe issue is archived, and new occurrences open a new issue
Archived for 90 daysThe issue is deleted, with its incidents, comments and state history
A fingerprint that never became an issueForgotten after 24 hours without a new occurrence

Alerts and audit history

DataKept for
Alert rule checks (each evaluation, with its observed value)365 days
Organization audit log (Settings → Audit Log)6 years (2,190 days)

Maple Local

Maple Local keeps logs and traces for 30 days and metrics for 90, and lets you raise the floor for raw data. See Your data. To keep history longer, export it with archives.