Token limits
Each client token has four limits:
| Limit | Default | Highest |
|---|---|---|
| Requests | 500 per second | 5,000 per second |
| Bytes | 50 MiB per second | 500 MiB per second |
| Daily bytes | 20 GiB per UTC day | 200 GiB per UTC day |
| Errors | 6,000 per minute | 60,000 per minute |
Over a rate, the endpoint answers 429 with Retry-After, and the SDK waits. Over the daily
budget, Retry-After is the next UTC midnight, and the SDK stops sending from that browser
until then. Each user’s address also has its own request rate.
Change a token’s limits in the console (Tokens > edit), with
ezgh obs browser-apps tokens update (--requests-per-second, --bytes-per-second,
--bytes-per-day, --errors-per-minute, each a number or default), or in the API’s limits.
Lower limits protect your bill from a page that misbehaves or a token someone copies. To go above
the highest values, contact support.
Spike protection
Errors over the token’s errors-per-minute are dropped before they’re counted or billed, so a
bad deploy that throws on every page can’t run up your bill. A request’s errors are kept or dropped
together. Spans and view events keep arriving, so performance data is unaffected, and the request
still succeeds (its partial_success counts the dropped records).
The token’s row in the console’s Tokens tab shows how many errors were dropped today (UTC),
and so do ezgh obs browser-apps tokens list and get (errorsDroppedToday in the API).
Requests
| Limit | Value |
|---|---|
| Paths | /v1/traces and /v1/logs only. There’s no /v1/metrics (404): EZGH generates the metrics |
| Request size | 1 MiB compressed and 8 MiB uncompressed, otherwise 413 |
| Format | OTLP JSON, as text/plain or application/json; protobuf is 415 |
| Credentials | The token in ?ct= only. An Authorization header is 400 |
Your organization’s and the dataset’s ingest rates also apply, and so do the record limits.
Generated metrics
The RUM metrics are free: they aren’t
counted as ingested or stored bytes. view_name keeps 500 names per environment and application
each hour, and an environment has up to 20,000 RUM series, apart from its span metrics; past
either, new series are counted under view_name="__other__".
Quotas
| Quota ID | Name | Scope | Default | Adjustable |
|---|---|---|---|---|
obs.clientTokens.perProject |
Client tokens per project | Project | 50 | Yes, up to 500 |
ezgh quotas get obs.clientTokens.perProject --scope-key <project ID>Creating a token over the quota is 409 quota_exceeded. Deleting a token gives its place back.
Issues and source maps have no quota.
Source maps
| Limit | Value |
|---|---|
| Storage | 10 GiB per project; a commit over it is 409 storage_limit_exceeded |
| Retention | A release’s maps are deleted 90 days after an error last used them |
| Releases | An application keeps its newest 50 releases |
| Chunks | At most 8 MiB each; chunks/missing takes up to 1,000 hashes |
| Commit | At most 1,000 files |
Issues
An issue is deleted 30 days after its environment’s logs retention has passed its last event.
SDK
| Limit | Value |
|---|---|
Custom attributes (setAttributes) |
32 |
| Breadcrumbs on an error | The last 50, at most 16 KB |
| The same error, per page | 10 a minute; the rest are counted on the next one sent |
| Offline queue | 1 MB, in memory, oldest dropped first |
| Session | Ends after 30 minutes of inactivity, or 4 hours |
| Internal errors | The SDK turns itself off after 10 on a page |
Session timelines
A session timeline shows up to 2,000 items, the nearest to the event it was opened from.