Skip to content

Conversation

@Flash0ver
Copy link
Member

@Flash0ver Flash0ver commented Dec 2, 2025

See also https://develop.sentry.dev/sdk/telemetry/logs/.

Other

If debug is set to true in SDK init, calls to the Sentry logger API should also print to the console with the appropriate log level. This will help debugging logging setups.


CHANGES

  • When SentryOptions.Debug is enabled and a SentryLog is captured via the SDK-Logger-APIs, but not filtered via BeforeSendLog, then also print the message to the standard output stream.

TODO

  • also write to Trace/Listeners
    • in which cases?
  • CHANGELOG entry

@Flash0ver Flash0ver self-assigned this Dec 2, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2025

Fails
🚫 Please consider adding a changelog entry for the next release.
Messages
📖 Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

### Features

- when Debug is true then SDK-Logger also prints to the Console ([#4785](https://github.com/getsentry/sentry-dotnet/pull/4785))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description or adding a skip-changelog label.

Generated by 🚫 dangerJS against 5870b39

@Flash0ver Flash0ver changed the title feat(logs): when Debug is true then SDK-Logger also emits diagnostic logs feat(logs): when Debug is true then SDK-Logger also prints to the Console Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants