diff --git a/develop-docs/sdk/telemetry/logs.mdx b/develop-docs/sdk/telemetry/logs.mdx index 68787b42352e5..37334f6d54432 100644 --- a/develop-docs/sdk/telemetry/logs.mdx +++ b/develop-docs/sdk/telemetry/logs.mdx @@ -305,13 +305,20 @@ If there are no `sentry.message.parameter.X` attributes included in the log, the #### SDK Integration Attributes -If a log is generated by an SDK integration, the SDK should also set the `sentry.origin` attribute, as per the [Trace Origin](/sdk/telemetry/traces/trace-origin/) documentation. It is assumed that logs without a `sentry.origin` attribute are manually created by the user. +If a log is generated by an SDK integration, the SDK should also set the `sentry.origin` attribute, as per the [Trace Origin](/sdk/telemetry/traces/trace-origin/) documentation. -```json -{ - "sentry.origin": "auto.db.graphql" -} -``` +Logs can be generated in three ways: + +1. User calls Sentry’s Logging API directly: SDKs MUST NOT send a `sentry.origin`. As logs are charged based on size, we want to minimize the size of logs, and we **intentionally deviate** from the original [Trace Origin](/sdk/telemetry/traces/trace-origin/) documentation. + +2. Captured from a logging library: Use `auto.log.` format. where `` is the relevant integration. For example, the .NET Serilog library emits: + ```json + { "sentry.origin": "auto.log.serilog" } + ``` +3. Auto-emitted logs from other instrumented systems: Use the `auto..` format as outlined in [Trace Origin](/sdk/telemetry/traces/trace-origin/) documentation. + ```json + { "sentry.origin": "auto.db.prisma" } + ``` #### User Attributes diff --git a/develop-docs/sdk/telemetry/traces/span-operations.mdx b/develop-docs/sdk/telemetry/traces/span-operations.mdx index 37c1566ebb88d..bd401be6a0237 100644 --- a/develop-docs/sdk/telemetry/traces/span-operations.mdx +++ b/develop-docs/sdk/telemetry/traces/span-operations.mdx @@ -265,6 +265,7 @@ Messages/Queue spans are expected follow OpenTelemetry's [Messaging](https://git | graphql | | | grpc | | | http | | +| log | | | mark | | | measure | | | middleware | |