Question

A network automation service writes structured events to a centralized syslog collector using the standard Python logging module with a SysLogHandler. Operators report that INFO-level 'config pushed' messages arrive at the collector, but WARNING-level messages about partial rollback failures never appear. The application code calls logger.warning() at the correct points, and the collector is confirmed reachable. Reviewing the initialization code, you find: logger.setLevel(logging.INFO) on the logger and handler.setLevel(logging.ERROR) on the SysLogHandler. What is the root cause and correct fix?

Accepted Answer

The handler's level is set to ERROR, so WARNING records are dropped at the handler; lower the SysLogHandler level to WARNING (or below) so warnings are emitted.

Answer

The logger level of INFO blocks WARNING because WARNING is numerically lower; raise the logger level to WARNING to allow the messages through.

Answer

SysLogHandler cannot transmit WARNING severity over UDP; switch the transport to TCP so the warning facility code is preserved.

Answer

The syslog collector must be configured with a facility filter matching WARNING; no application code change is required.