impr: Record client report when dropping in beforeSendLog#7379
impr: Record client report when dropping in beforeSendLog#7379philipphofmann merged 3 commits intogetsentry:mainfrom
Conversation
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog. This PR will not appear in the changelog. 🤖 This preview updates automatically when you update the PR. |
philipphofmann
left a comment
There was a problem hiding this comment.
Thanks a lot. Please also add a test for this in the SentryClient tests and add an entry to the changelog.
philipphofmann
left a comment
There was a problem hiding this comment.
Thanks a lot @antigluten
|
@cursoragent review |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7379 +/- ##
=============================================
+ Coverage 85.223% 85.249% +0.025%
=============================================
Files 478 478
Lines 28580 28582 +2
Branches 12430 12434 +4
=============================================
+ Hits 24357 24366 +9
+ Misses 4177 4169 -8
- Partials 46 47 +1
... and 6 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
|
@cursor review |
📜 Description
The SDK must record a client report with
kSentryDiscardReasonBeforeSendwhen it drops a log in beforeSendLog.We should tackle this issue after merging #7334, as this PR moves
beforeSendMetricto a different location.#skip-changelog
💡 Motivation and Context
Resolves #7336
💚 How did you test it?
📝 Checklist
You have to check all boxes before merging:
sendDefaultPIIis enabled.