Quotas, retention and scrubbing

Quotas

Each plan includes, every month, a number of errors and of replays and gigabytes of spans and of logs, and caps how many uptime monitors and dashboards you keep. Settings → Billing shows each meter's limit, what each source has used and where the month is heading.

Past the limit there is no surprise invoice. For the first tenth over, one in ten is kept; after that, nothing more is kept until the month turns or a pack is added. Workspace owners hear when a meter passes its limit and again when it stops keeping anything. Metrics and uptime checks are not metered.

On a paid plan, an owner can turn on auto top-up for a meter and pick how many packs it may buy a month. When less than a tenth of a pack is left, one more is charged to the card the plan is paid with, and the limit moves before anything is left out. Past that number, the cap holds as above. If the card is declined or the bank asks you to confirm, auto top-up stops, this month and after, until an owner presses Try again in Billing.

Retention

Each kind is kept for its own number of days, chosen in Settings → Signals, up to the plan's ceiling:

• Errors: 90 days unless you choose otherwise.
• Traces: 30 days.
• Logs: 14 days.
• Replays: 30 days.

A plan with a lower ceiling keeps each kind no longer than it. Metrics are kept for 15 days as sent and 13 months as hourly totals. Shortening retention deletes what is older straight away, so Rezee asks before it does.

What is filtered before it is stored

Whatever you send, these never reach storage:

• Authorization and cookie headers, API key headers, and the headers that carry a client's IP address.
• Values under keys that name a password, secret, token, API key, cookie, session, card number, CVV or private key.
• Bearer and Basic credentials, JWTs, and well-known tokens such as Stripe, GitHub, Slack and AWS keys, wherever they appear in text.
• Query parameters that carry a token, key, secret or password.
• Email addresses and card numbers in text.

The id and email of the user your app names on an event are kept as sent, since you sent them on purpose; their IP address is not.

Your own scrub rules

Add up to 30 rules in Settings → Signals, and try them on sample text before saving:

• A field, such as order_ref: its value is filtered wherever it appears.
• A pattern, such as ORD-######: any text that matches is filtered. # is a digit, ? is a letter or digit, and a * stands for up to 32 characters that are not spaces; a pattern may hold one. Everything else matches itself, in any case. Patterns are not regular expressions, so one can never slow ingest down.

Event, trace and span ids and timestamps are never touched by a pattern.

Who reads logs and replays

Logs and replays can each be limited to one team in Settings → Signals, since they tend to hold more than errors do. Replays are masked in the browser first; the built-in filters and your patterns then run over them as over everything else, and your field rules over the pages a replay lists.