Skip to content

Conversation

@joshuaruesweg
Copy link

This change ensures that the logger name is logged accordingly as an attribute in Sentry. Previously, the documentation stated that this would be the case, but in practice, the logger name was never logged.

@joshuaruesweg joshuaruesweg force-pushed the master branch 2 times, most recently from 6391850 to 09ac701 Compare January 12, 2026 13:43
This change ensures that the logger name is logged accordingly as an attribute in Sentry. Previously, the documentation stated that this would be the case, but in practice, the logger name was never logged.
@stayallive
Copy link
Collaborator

Im am not contesting this might be useful but for completeness I don't think I see anywhere we are supposed to be logging the channel name: https://docs.sentry.io/platforms/php/guides/laravel/logs/

What use case do you have for this specifically?

@joshuaruesweg
Copy link
Author

joshuaruesweg commented Jan 19, 2026

The documentation here states that the channel name is logged as a “logger” attribute and represented in Sentry. However, I couldn't find this attribute anywhere, so I added it (and renamed it to channel).

In principle, this feature is very useful when working with different channels. For example, we have a wide variety of loggers, in addition to the default logger, that log specific things. Among other things, we have a payment logger that logs a wide variety of payment-related information. It is important for us to be able to filter and view this log protocol. In principle, we could of course also use the file driver to view the log, but in the long term we wanted to make the logs available in Sentry as well and be able to filter them there so that we can view only the payment logs, for example.

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