chore: Deprecate the enable_logs option - #1299
Open
szokeasaurusrex wants to merge 1 commit into
Open
Conversation
szokeasaurusrex
marked this pull request as ready for review
August 13, 2026 11:21
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit c98feda. Configure here.
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
giortzisg
approved these changes
Aug 13, 2026
Providing the ability to disable sending logs is somewhat of a footgun, as this flag can prevent all Sentry logs from being sent, so this change turns that option into a no-op, ensuring logs are always enabled. Logs are only sent when users explicitly record them with the logging APIs we provide or when one of the integrations that captures logs (currently `tracing`, `log`, or `slog`) are enabled. Users who do not want logs can either stop using the logging APIs, disable the integrations which capture logs, or adjust said integrations' configurations. Resolves [#1297](#1297) Resolves [RUST-274](https://linear.app/getsentry/issue/RUST-274/deprecate-and-no-op-ify-enable-logs)
szokeasaurusrex
force-pushed
the
szokeasaurusrex/enable-logs-deprecation
branch
from
August 13, 2026 13:53
1d9ba55 to
fd719e1
Compare
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
2 participants
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.
Providing the ability to disable sending logs is somewhat of a footgun, as this flag can prevent all Sentry logs from being sent, so this change turns that option into a no-op, ensuring logs are always enabled.
Logs are only sent when users explicitly record them with the logging APIs we provide or when one of the integrations that captures logs (currently
tracing,log, orslog) are enabled. Users who do not want logs can either stop using the logging APIs, disable the integrations which capture logs, or adjust said integrations' configurations.Resolves #1297
Resolves RUST-274