Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions develop-docs/sdk/foundations/transport/rate-limiting.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -94,14 +94,20 @@ While these [data categories](https://github.com/getsentry/relay/blob/master/rel
- `security`: Events with event_type `csp`
- `attachment`: Attachment bytes stored (unused for rate limiting)
- `session`: Session update events
- `profile`: Profiling events
- `profile_chunk`: Continuous Profiling chunks
- `replay`: Session Replays
- `feedback`: User Feedbacks
- `trace_metric`: Metric type events.
- `trace_metric_byte`: Metric bytes stored.
- `internal`: a sentry/system internal event[^internal]

Relay utilizes various data categories for profiles, allowing separate rate limiting for each. SDKs must implement the same logic applied to other data categories and discard the associated profiling data when a rate limit is active:

- `profile`: Profiling events for backend platforms.
- `profile_chunk`: Continuous Profiling chunks for backend platforms.
- `profile_chunk_ui`: Continuous Profiling chunks for UI platforms.
- `profile_backend`: Transaction profiles for backend platforms.
- `profile_ui`: Transaction profiles for UI platforms.

- **Scope**: The unit / model in Sentry that quotas are enforced for.
- `organization`
- `project`
Expand Down
Loading