Usage and data handling
This page covers how much monitoring data your plan takes in, how long it's kept, and how to delete it. For what your SDKs keep out of the data in the first place, see redaction.
Monthly data allowance
Each plan includes an amount of monitoring data per month, counted as the bytes of the events your SDKs send: logs, traces, metrics and uploaded source files.
| Plan | Data per month | Raw events kept for |
|---|---|---|
| Free | 100 MB | 7 days |
| Starter | 1 GB | 30 days |
| Growth | 5 GB | 90 days |
| Business | 20 GB | 180 days |
| Enterprise | By contract | 365 days by default, or as your contract says |
The counter resets each month. An SDK retrying a request is not charged twice.
Charts over longer ranges read hourly rollups, which outlive the raw events. See logs.
When you reach your allowance
Once your allowance for the month is used up, new events are refused until it resets or you upgrade. See your usage under Billing, or with octri orgs usage.
Turning monitoring off
Turning monitoring off for a project blocks ingestion right away, including from SDKs already installed. Turning it back on issues new credentials, so old ones stay revoked.
Deleting data
One person's data
To act on a data subject request, open the monitoring connection settings, choose Erase a user's data, and confirm the user's ID. This needs an owner or admin, and it's recorded in your audit trail. If the monitoring service can't be reached at that moment, the erasure is queued and retried hourly.
A whole project
Deleting a project purges its monitoring data too. If the purge can't finish at that moment, it's retried hourly.
Legal documents
The Data Processing Addendum and its Monitoring addendum describe field by field what an event contains, where it's stored, how long it's kept, and who processes it.