Conversation
ericapisani
approved these changes
Apr 1, 2026
|
Hi, this just became even more confusing I think. There is no alternative to the "old" We do not make use of Sentry logs, so how are we supposed to replace a deprecated handler with an alternative that does not support the same behaviour? Can you elaborate what we need to do? Thank you. |
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
3 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.
Adds a deprecation notice to the old Sentry
Handlerthat is used to convert log messages into Sentry errors. TheHandlerexisted in a time where Sentry had no native log support yet we still allowed to capture logs in some way.Now that we have the
LogsHandler, it is becoming increasingly confusing which one to use and what they are really doing, so we want to deprecate it for now and point everyone towards the new logs handler.