On Fri, 03 Mar 2017 04:12:30 -0800, David Lang wrote:
> On Fri, 3 Mar 2017, Alexey Zaharov via rsyslog wrote:
>
>> Hello All,
>>
>> Is there anyway to force rsyslog to catch particular level for given
>> facility?
>>
>>
>> I cannot catch `info` and `debug` messages with following line in
>> `/etc/rsyslog.d/70-op.conf`:
>>
>> ```
>> local3.=debug;local3.=info;local3.* /var/log/op.log ```
>
> that line should but all local3 messages in that file. Is that not
> what's happening?
>
> David Lang
This is correct.
Calls (python3.3 logging)
```
handler = logging.handlers.SysLogHandler(
address = ('192.168.50.41',514),
facility = 19) # LOG_LOCAL3 = 19
logger = logging.getLogger()
logger.addHandler(handler)
logging.critical('CRITICAL BEGIN')
logging.debug('test debug')
logging.info('test info')
logging.warning('test warning')
logging.error('test error')
logging.critical('test critical')
logging.critical('CRITICAL END')
```
Output
```
Mar 3 12:03:26 CRITICAL BEGIN
Mar 3 12:03:26 test warning
Mar 3 12:03:26 test error
Mar 3 12:03:26 test critical
Mar 3 12:03:26 CRITICAL END
```
As you can see debug and info are missing.
--
Regards. Alexey.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
