refactor(telemetry): port to sentry-go v0.46 Tags API#85
Merged
Conversation
added 2 commits
May 10, 2026 11:50
Breaking: removes Event.Extra and Scope.SetExtra (upstream sentry-go#1274). Subsequent commit ports internal/telemetry to Tags-based API. Build is intentionally broken on this commit -- see docs/plans/2026-05-10-sentry-go-extra-migration.md. Refs: #70 (closed group bump that included this version), Vikunja #1139.
sentry-go v0.46 (PR getsentry/sentry-go#1274) removed Event.Extra and Scope.SetExtra. Migrate the one writer (CaptureError's error_type field) to SetTag -- error_type is already a string label, so SetTag is the natural target. Strip Extra-handling from the privacy filter (applyPrivacyFilters, applyPrivacyFiltersWithLogging, and the now- unused removePrivacyExtraFields helper). Remove the Extra column from EventSummary and update telemetry_test.go to round-trip via Tags. The privacy filter retains the same structural behavior for Tags and Contexts (no changes to which keys are stripped). error_type as a Tag is non-PII (it's a parsed runtime error category, e.g. 'Nil Pointer Dereference', generated by parseErrorType from the *scrubbed* message -- see sentry.go::parseErrorType + privacy.ScrubMessage). Refs: Vikunja #1139, #70 (closed group bump that included this version).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
getsentry/sentry-go0.42.0 → 0.46.2scope.SetExtrawriter inCaptureErrortoSetTag(the value is already a string)Event.Extrareferences from the privacy filter andEventSummarymock — Extra was removed from sentry-go in upstream PR feat!: remove SetExtra getsentry/sentry-go#1274TestEventSummaries(telemetry_test.go) to round-trip via TagsTest plan
go test ./internal/telemetry/ -race -count=1passestask lintclean (0 issues across 29 active linters)event.Extra/SetExtrareferences ininternal/Notes
error_typewas rendered under "Additional Data" in Sentry; it now appears under "Tags". Same data, different UI section.error_typeis a parsed runtime category (e.g."Nil Pointer Dereference") generated byparseErrorTypefrom the scrubbed message, so no PII path that wasn't already there.scope.SetFingerprintis unchanged.Background
PR #70 (the dependabot go-minor-patch group bump) was closed because it bundled this breaking sentry-go upgrade with 15 unrelated bumps. After this lands, dependabot will re-raise the remaining 15 as a clean group.
Refs: Vikunja #1139, plan at
docs/plans/2026-05-10-sentry-go-extra-migration.md🤖 Generated with Claude Code