Repository navigation
ref(logs): Promote structured logs APIs - #6424
Merged
Merged
Conversation
📲 Install BuildsAndroid
|
adinauer
marked this pull request as ready for review
October 30, 2026 09:34
adinauer
requested review from
0xadam-brown,
markushi,
romtsn and
runningcode
as code owners
October 30, 2026 09:34
runningcode
approved these changes
Oct 30, 2026
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
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.
📜 Description
Remove the remaining
@ApiStatus.Experimentalannotations from the structured logs options and low-level capture method:SentryOptions.getLogs()SentryOptions.setLogs(...)SentryClient.captureLog(...)Batched transport plumbing remains internal. This changes API status only; log capture behavior remains unchanged.
💡 Motivation and Context
The public structured logger API and log configuration have been hardened through batching, integration support, shutdown handling, PII fixes, trace linking, and reentrancy protection. The remaining annotations no longer reflect the maturity of the API.
Crash durability for buffered logs remains tracked separately in #4690 and can be implemented without redesigning the public capture API.
Refs #6408
💚 How did you test it?
Ran:
Both commands completed successfully, and API generation produced no API dump changes.
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Improve crash durability for buffered logs separately without changing the public logging API.