feat: Update logs spec to mention message template constraint (#14759)

AbhiPrasad · web-flow · commit e7903ab04ac0 · 2025-08-28T11:30:47.000-04:00
diff --git a/develop-docs/sdk/telemetry/logs.mdx b/develop-docs/sdk/telemetry/logs.mdx
@@ -299,6 +299,8 @@ If the log was paramaterized the SDK should attach the following
 }
 ```
 
+If there are no `sentry.message.parameter.X` attributes included in the log, then the SDK MUST NOT attach a `sentry.message.template` attribute. This is important because it reduces duplicate content in the log and makes PII processing in Sentry much easier as only we don't have to duplicate processing between the log message and the `sentry.message.template` attribute.
+
 #### 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.

Original file line number	Diff line number	Diff line change
`@@ -299,6 +299,8 @@ If the log was paramaterized the SDK should attach the following`
`299`	`299`	`}`
`300`	`300`	```
`301`	`301`
	`302`	+If there are no `sentry.message.parameter.X` attributes included in the log, then the SDK MUST NOT attach a `sentry.message.template` attribute. This is important because it reduces duplicate content in the log and makes PII processing in Sentry much easier as only we don't have to duplicate processing between the log message and the `sentry.message.template` attribute.
	`303`	`+`
`302`	`304`	`#### SDK Integration Attributes`
`303`	`305`
`304`	`306`	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.