Bug 266523 - logging.handlers.SysLogHandler no longer works with 2+ level hierarchical logging provided-name in TAG after RFC-5424 changes
Summary: logging.handlers.SysLogHandler no longer works with 2+ level hierarchical log...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-20 19:22 UTC by Enji Cooper
Modified: 2022-09-20 19:33 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enji Cooper freebsd_committer freebsd_triage 2022-09-20 19:22:00 UTC

    
Comment 1 Enji Cooper freebsd_committer freebsd_triage 2022-09-20 19:28:58 UTC
The logging package in python supports hierarchical logger names, e.g., foo.bar.baz. The beforementioned logger name [can] inherit settings from "foo" or "foo.bar".

The changes made in 1a874a126a54fdc188cebd0c58579851c37d1814 unfortunately broke this capability, breaking application code in the process which handles filtering out specific names to specific log sinks; now all logging with dotted names goes to /var/log/messages .

The strictness was relaxed in 3b4cc56e524ac947ba0e6571e2c455139c2839ec for PRI. Similar treatment needs to be applied for TAG as well.

References:
- https://docs.python.org/3/library/logging.html#logger-objects