Problem Statement
We want to deprecate Monolog\Handler but this means that converting log messages with a certain level to Sentry Issues will no longer work. For people using Sentry logs, this might be a non issue but if someone is not using Logs, the removal feels like they have to do more work to set up alerts and get a similar functionality.
Solution Brainstorm
Add a handler that just converts log messages with a certain level to issues. Give it a proper name like LogToSentryIssueHandler so that it's clear it only does one thing. Avoid adding more functionality and generic names to not repeat the mistake of Monolog\Handler.
If exception -> issue and log -> issue is desired, the solution would be to have two handlers, each handling their respective part
Origin: #2051 (comment)
Problem Statement
We want to deprecate
Monolog\Handlerbut this means that converting log messages with a certain level to Sentry Issues will no longer work. For people using Sentry logs, this might be a non issue but if someone is not using Logs, the removal feels like they have to do more work to set up alerts and get a similar functionality.Solution Brainstorm
Add a handler that just converts log messages with a certain level to issues. Give it a proper name like
LogToSentryIssueHandlerso that it's clear it only does one thing. Avoid adding more functionality and generic names to not repeat the mistake ofMonolog\Handler.If
exception -> issueandlog -> issueis desired, the solution would be to have two handlers, each handling their respective partOrigin: #2051 (comment)