On Apr 14, 2015, at 11:43 PM, David Lang da...@lang.hm wrote:
On Wed, 15 Apr 2015, Ezell, Matthew A. wrote:
Hello-
What is the current best practice for a portable application to get
structured data to rsyslog?
... gets JSON printed to the log. That may be undesirable in the common
On Wed, Apr 15, 2015 at 6:25 PM, Dave Caplinger
davecaplin...@solutionary.com wrote:
On Apr 14, 2015, at 11:43 PM, David Lang da...@lang.hm wrote:
On Wed, 15 Apr 2015, Ezell, Matthew A. wrote:
[...]
what I do is to take whatever message was output and then run mmjsonparse
against
What I do on my relay boxes
$template structured_forwarding,%pri%%timereported% %hostname% %syslogtag%
@cee:%$!%\n
module(load=imudp timerequery=4)
module(load=imtcp maxsessions=1000)
module(load=mmjsonparse)
input(type=imudp port=514 ruleset=relay)
input(type=imtcp port=514 ruleset=relay)
Thanks from me as well. Will merge in the not so distant future. I'd
like to have a deeper look at the changes and as we are weeks away
from next release, it probably doesn't hurt to keep the PR a couple of
days open (while I am deeply inside lognorm ;)).
Rainer
2015-04-15 5:21 GMT+02:00
Sounds good.
Realized I haven't posted PR link here yet.
PR: https://github.com/rsyslog/rsyslog/pull/303
On Wed, Apr 15, 2015 at 2:55 PM, Rainer Gerhards
rgerha...@hq.adiscon.com wrote:
Thanks from me as well. Will merge in the not so distant future. I'd
like to have a deeper look at the
We keep our logs in JSON format and don't find it to be a drawback. We
have logs searchable in elasticsearch - and for working with logs on disk,
have a small program that logs can be piped through that strips out
everything but the json which makes it very easy to pipe logs to jq (a
command line
6 matches
Mail list logo
