Limits
An instance limits what each request can cost, so that one project cannot slow the others down. A request over a rate limit gets 429 with a Retry-After header: the seconds to wait.
Events
Section titled “Events”Each batch
Section titled “Each batch”| Rule | Limit |
|---|---|
| Body | 64 KB, not compressed. Content-Encoding is not supported. |
| Events in a batch | 1 to 50 |
| Event ID | A UUID |
| Event name | 1 to 200 characters, without control characters |
| Page URL | An http or https URL of up to 8,192 characters, with a path of up to 2,048 |
| Properties | A flat object: at most 30 keys of up to 100 characters. Values are strings of up to 500 characters, numbers, booleans, or null. At most 8 KB in total. |
| Environment | 1 to 64 letters, digits, ., _, or -, starting with a letter or digit |
| Release | 1 to 200 characters, without spaces or control characters |
| User ID | 1 to 200 characters, without control characters |
| Age | An event that happened more than 24 hours before it was sent is not stored. |
The instance keeps only the path and the five UTM tags of a page’s URL. Each UTM value is cut to 200 characters.
| Limit | Burst | Sustained |
|---|---|---|
| Browser requests, for each client IP address | 120 requests | 2 requests a second |
| Server event requests, for each IP address | 600 requests | 50 requests a second |
| Events, for each project | 2,000 events | 200 events a second |
| Events, for the whole instance | Ten seconds’ worth | INSTANCE_EVENTS_PER_SECOND, 600 by default |
A project’s browser and server events share the project’s budget.
Retention
Section titled “Retention”A project keeps its events until its owner or an admin sets a limit in the project’s settings. The worker deletes events older than the limit.
Heatmaps
Section titled “Heatmaps”Each pageview
Section titled “Each pageview”| Rule | Limit |
|---|---|
| Clicks | 100. Later clicks are only counted. |
Element name (data-ottertrail-name) |
1 to 64 letters, digits, spaces, ., _, :, /, or -, starting with a letter or digit |
| Element’s place in the page | The nearest 24 steps, at most 512 characters |
Each batch
Section titled “Each batch”| Rule | Limit |
|---|---|
| Body | 64 KB |
| Records in a batch | 1 to 50, from 1 to 50 pages |
| Age | A record that happened more than a day before it was sent is not stored. |
| Limit | Burst | Sustained |
|---|---|---|
| Requests, for each client IP address | 120 requests | 2 requests a second |
| Records, for each client IP address | 400 records | 40 records a second |
| Records, for each project | 2,000 records | 100 records a second |
| Records, for the whole instance | 6,000 records | 300 records a second |
Heatmaps have their own budgets, so they cannot crowd out a site’s events. The budgets are provisional until they are measured on real sites.
Retention
Section titled “Retention”90 days, whatever the project’s setting for events.
The heatmap overlay
Section titled “The heatmap overlay”| Rule | Limit |
|---|---|
| Links, for each user | 20, then 20 a minute |
| A link | Works once, within 5 minutes |
| The overlay’s session | 30 minutes |
Errors
Section titled “Errors”| Field | Limit |
|---|---|
| Type | 1 to 200 characters |
| Message | Up to 2,000 characters |
| Stack | Up to 16,000 characters |
| Errors for each page load | 25, and each identical error one time |
Source maps
Section titled “Source maps”| Rule | Limit |
|---|---|
| Size | 25 MiB after it is unpacked |
| Lines | 100,000 |
| Segments | 1,000,000 |
| Path | Up to 1,024 characters |
| Requests, for each IP address | A burst of 200, then 5 a second |
| Storage, for the whole instance | SOURCE_MAP_STORAGE_BYTES, 1 GiB by default |
Session replays
Section titled “Session replays”| Rule | Limit |
|---|---|
| Kept | 30 days |
| Storage, for the whole instance | REPLAY_STORAGE_BYTES, 2 GiB by default |
Telemetry
Section titled “Telemetry”Each request
Section titled “Each request”| Rule | Limit |
|---|---|
| Size | 16 MiB after it is unpacked |
| Messages | A million: the records, attributes, and values in the request |
| Requests at once | 4 for each project |
Each record
Section titled “Each record”| Rule | Limit |
|---|---|
| Attributes | 128 for each record. The rest are dropped and counted. |
| Attribute value | 4 KB. Longer values are cut. |
| Resource attributes | 8 KiB in all |
| Labels (service, scope, severity text, event name, unit) | 256 characters |
| Log body | 64 KB. Longer bodies are cut. |
| Span events and links | 128 of each for each span |
| Histogram bounds | 64. A point with more is refused. |
| Time | Within the retention, and at most one hour in the future. Other records are refused. |
Budgets
Section titled “Budgets”| Limit | Burst | Sustained |
|---|---|---|
| Each project | 50,000 | 5,000 a second |
| The whole instance | 150,000 | 15,000 a second |
A request costs one unit for each record. A request with many attributes or a large resource can cost more. Telemetry has its own budgets, so it cannot crowd out a site’s events.
A request that costs more than a project’s whole budget is refused with 413. In the Collector, keep send_batch_max_size at 50,000 or less.
Retention
Section titled “Retention”TELEMETRY_RETENTION_DAYS, 30 days by default, from 1 to 365.
Webhooks and alerts
Section titled “Webhooks and alerts”| Rule | Limit |
|---|---|
| Answer time | 10 seconds |
| Attempts | 8, in about an hour |
| Deliveries for each channel | 60 an hour |
| Notifications for each rule | 20 an hour, then one alert.held_back |