Skip to content

feat(logs): Add sentry.replay_id to logs spec #14838

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 10, 2025
Merged

feat(logs): Add sentry.replay_id to logs spec #14838

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8a00d5d
feat(logs): Add `sentry.replay_id` to logs spec
AbhiPrasad Sep 8, 2025
0602f2a
remove future note
AbhiPrasad Sep 10, 2025
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
14 changes: 13 additions & 1 deletion develop-docs/sdk/telemetry/logs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -275,14 +275,16 @@ By default the SDK should attach the following attributes to a log:
3. `sentry.trace.parent_span_id`: The span id of the span that was active when the log was collected. This should not be set if there was no active span.
4. `sentry.sdk.name`: The name of the SDK that sent the log
5. `sentry.sdk.version`: The version of the SDK that sent the log
6. `sentry.replay_id`: The replay id of the replay that was active when the log was collected. This should not be set if there was no active replay.

```json
{
"sentry.environment": "production",
"sentry.release": "1.0.0",
"sentry.trace.parent_span_id": "b0e6f15b45c36b12",
"sentry.sdk.name": "sentry.javascript.node",
"sentry.sdk.version": "9.11.0"
"sentry.sdk.version": "9.11.0",
"sentry.replay_id": "36b75d9fa11f45459412a96c41bdf691"
}
```

Expand Down Expand Up @@ -393,6 +395,16 @@ SDKs should aim to have it so that console/logger integrations create logs as pe

If SDK authors feel the need, they can also introduce additional options to beyond `enableLogs`/`enable_logs` to gate this functionality. For example an option to control log appenders added via external config like with `Log4j` in the Java SDK.

### Behaviour with other Sentry Telemetry

#### Tracing

Logs should be associated with traces if possible. If a log is recorded during an active span, the SDK should set the `sentry.trace.parent_span_id` attribute to the span id of the span that was active when the log was collected.

#### Replays

Logs should be associated with replays if possible. If a log is recorded during an active replay, the SDK should set the `sentry.replay_id` attribute to the replay id of the replay that was active when the log was collected.

### Other

If `debug` is set to `true` in SDK init, calls to the Sentry logger API should also print to the console with the appropriate log level. This will help debugging logging setups.
Expand Down
Loading