On Tue, Mar 8, 2016 at 9:54 AM, Florian Riedl <fri...@adiscon.com> wrote:
> Hi all,
>
> We have released rsyslog 8.17.0.
I just started testing this release and with the same config I was
using for 8.13 (which may be the issue) I'm seeing the following
incomplete JSON being dropped in my rsyslog stats log for "global".
I'm including the lines before and after for context.
2016-03-09T15:49:29.427521+00:00 01.syslog.dev.lax1 rsyslogd-pstats:
{"name":"imudp(w0)","origin":"imudp","called.recvmmsg":4,"called.recvmsg":0,"msgs.received":2}
2016-03-09T15:50:30.150578+00:00 01.syslog.dev.lax1 rsyslogd-pstats:
{"name":"global","origin":"dynstats",
2016-03-09T15:50:30.150732+00:00 01.syslog.dev.lax1 rsyslogd-pstats:
{"name":"action
0","origin":"core.action","processed":0,"failed":0,"suspended":0,"suspended.duration":0,"resumed":0}
I'm not sure if this indicates a configuration issue or a bug, but
wanted to pass it along.
My pstats config looks like this (looking back over the docs, I am not
sure anymore why I broke out the file handler into a ruleset instead
of using log.file):
module(
load="impstats"
interval="60"
format="json"
ruleset="pstats")
ruleset(
name="pstats"
queue.type="FixedArray") {
action(
type="omfile"
file="/var/log/rsyslog.stats.log")
}
I also tried this format (no ruleset) with the same results:
module(
load="impstats"
interval="60"
format="json"
log.file="/var/log/rsyslog.stats.log")
Thanks.
Andy
_______________________________________________
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.
