mirror of
https://github.com/Seldaek/monolog.git
synced 2026-04-25 23:55:56 +03:00
[GH-ISSUE #1892] Log level not compliant with rfc5424 #810
Labels
No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/monolog#810
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @anthosz on GitHub (May 31, 2024).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/1892
Hello,
Following https://github.com/Seldaek/monolog/blob/main/doc/01-usage.md#log-levels:

There is strange level for each severity especially if it's supposed to be compliant with rfc5424.
In fact, it's not really the case. According to https://datatracker.ietf.org/doc/html/rfc5424#section-6.2.1 (table 2): "Severity values MUST be in the range of 0 to 7 inclusive."
Could you please change it?
It can lead to some issues during parsing from some log parsers ootb.
Thank you!
@Seldaek commented on GitHub (Jun 28, 2024):
You can make sure your formatters use
$record->level->toRFC5424Level()to format stuff to get compliant levels if you care about the actual level used. The syslog formatter for example uses that.The internal levels are the way they are for BC reasons and I don't think they should be changed. Maybe something for v4 though if we could add a way to opt-in to it in v3 ideally.. I'll leave this open for now as reminder.
@anthosz commented on GitHub (Jun 28, 2024):
Thank you for your feedback and let's see :)