Quotas for Error Tracking

How many projects your organization can have, how many events, transactions and profiles it may send per minute, day and month, how much it may store, and how to raise a quota.

Last updated 18 November 2026View as Markdown
QuotaDescriptionDefaultTrialApplies toAdjustable
Error Tracking projectsProjects (DSNs) in the organization, across regions505OrganizationYes
Error events per minuteError events the organization may send per minute; more are refused with a rate-limit answer the SDKs honour20.000600OrganizationYes
Error events per monthError events the organization may send per calendar month: the spend guard, on by default. Raise it to send more1.000.00050.000OrganizationYes
Error events per dayError events the organization may send per UTC day; more are refused until midnight UTC with a rate-limit answer the SDKs honour200.0005.000OrganizationYes
Error Tracking storageBytes the organization stores in Error Tracking: events, transactions, profiles, attachments and source maps. Over it, new data is refused until retention frees space53.687.091.2002.147.483.648OrganizationYes
Transactions per minutePerformance transactions (pageloads, requests) the organization may send per minute; more are refused for transactions only, errors keep flowing20.000600OrganizationYes
Transactions per monthPerformance transactions the organization may send per calendar month: the spend guard for traces, on by default1.000.00050.000OrganizationYes
Profiles per minuteProfiles and profile chunks the organization may send per minute (a continuous profiler sends one chunk a minute per process); more are refused for profiles only2.00060OrganizationYes
Profiles per monthProfiles and profile chunks the organization may send per calendar month: the spend guard for profiling, on by default500.00010.000OrganizationYes

Generated from the quota descriptors: the numbers are the ones the API enforces.

  • Creating a project over Error Tracking projects is refused with 409 "Quota exceeded: Error Tracking projects (errors.projects) — …".
  • The per-minute, per-day and per-month quotas are enforced by the ingest: over one, it refuses that kind of data with a rate-limit answer, and the SDKs pause (see How events are received). Transactions and profiles have per-minute and per-month budgets of their own, so a burst of traces or profiles does not hold up errors; all of them count towards Error Tracking storage.
  • Error events per month is the guard on your spending: raise it to send more.
  • Over Error Tracking storage, new data of every kind is refused until retention frees space.

Fixed limits

These are not quotas and cannot be raised.

What Limit
Active DSN keys 20 per project
Retention 30, 60 or 90 days
Profiles kept the project's retention, at most 30 days
Sessions kept 90 days
Default alert addresses 20 per project
Alert rule actions 10 per rule
Alert rule quiet period 1 minute to 7 days
Upload token lifetime at most 1 hour
Upload tokens per CI run 20

Raise a quota

Request an increase under Service quotas in the Deutsche Cloud Console, or with the CLI (see Quotas):

dcloud quotas requests request-increase --quota-id errors.events-per-month \
  --requested-value 5000000 --reason "Launch traffic"

On a trial organization, ask Deutsche Cloud support to move it to standard quotas.

Did this page help you?