From 603170769b8a2b5962be1a6c84608653113774d3 Mon Sep 17 00:00:00 2001 From: Lukas Stracke Date: Fri, 28 Nov 2025 15:36:31 +0100 Subject: [PATCH 1/2] chore(github): Adjust `BUGBOT.md` rules to flag invalid op and origin values during review --- .cursor/BUGBOT.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.cursor/BUGBOT.md b/.cursor/BUGBOT.md index d70f36ff6c94..328810ced256 100644 --- a/.cursor/BUGBOT.md +++ b/.cursor/BUGBOT.md @@ -32,7 +32,11 @@ Do not flag the issues below if they appear in tests. - When calling any `startSpan` API (`startInactiveSpan`, `startSpanManual`, etc), always ensure that the following span attributes are set: - `SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN` (`'sentry.origin'`) with a proper span origin + - a proper origin must only contain [a-z], [A-Z], [0-9] and `_` characters. + - flag any non-conforming origin values as invalid and link to the trace origin specification (https://develop.sentry.dev/sdk/telemetry/traces/trace-origin/) - `SEMANTIC_ATTRIBUTE_SENTRY_OP` (`'sentry.op'`) with a proper span op + - Span ops should be lower case only, and use snake_case. The `.` character is used to delimit op parts. + - flag any non-conforming origin values as invalid and link to the span op specification (https://develop.sentry.dev/sdk/telemetry/traces/span-operations/) - When calling `captureException`, always make sure that the `mechanism` is set: - `handled`: must be set to `true` or `false` - `type`: must be set to a proper origin (i.e. identify the integration and part in the integration that caught the exception). From 2744eebb97d2cb3290acadad79a7bafd679f53ea Mon Sep 17 00:00:00 2001 From: Lukas Stracke Date: Fri, 28 Nov 2025 15:57:44 +0100 Subject: [PATCH 2/2] Update .cursor/BUGBOT.md --- .cursor/BUGBOT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.cursor/BUGBOT.md b/.cursor/BUGBOT.md index 328810ced256..891b91d50f90 100644 --- a/.cursor/BUGBOT.md +++ b/.cursor/BUGBOT.md @@ -32,7 +32,7 @@ Do not flag the issues below if they appear in tests. - When calling any `startSpan` API (`startInactiveSpan`, `startSpanManual`, etc), always ensure that the following span attributes are set: - `SEMANTIC_ATTRIBUTE_SENTRY_ORIGIN` (`'sentry.origin'`) with a proper span origin - - a proper origin must only contain [a-z], [A-Z], [0-9] and `_` characters. + - a proper origin must only contain [a-z], [A-Z], [0-9], `_` and `.` characters. - flag any non-conforming origin values as invalid and link to the trace origin specification (https://develop.sentry.dev/sdk/telemetry/traces/trace-origin/) - `SEMANTIC_ATTRIBUTE_SENTRY_OP` (`'sentry.op'`) with a proper span op - Span ops should be lower case only, and use snake_case. The `.` character is used to delimit op parts.