On 07/15/2013 11:52 PM, Rainer Gerhards wrote:
On Tue, Jul 16, 2013 at 8:47 AM, Rainer Gerhards
<[email protected]>wrote:
yup, but in a different flavor: I think everyone can pretend things if he
is able to reconfigure rsyslog. I think the point here is to provide the
necessary facility to rightful users. And if e.g. mmjsonparse always parses
into the root, you have essentially lost, you can't properly work with
subtrees. I remember we discussed adding a capability to write to different
subtrees, not sure though if we did implement it.
I just checked: unfortunately we did not yet do that.
that would solve my problem I think, if the parser would put data
into a user specified subtree instead of root of json.
We are using the dev version (latest packages from adiscon ubuntu
repository), just about to release it to production (not a huge one, few
servers, maybe a million messages per day). Would definitely at least
test the version with parsing into a subtree.
curious: why all the discussions only talk about one json tree. Why
not have several named json trees? Then whenever referring to json one
would specify which tree to use. Technically it's no different than
having one tree but mentally it might be easier to manage (and to keep
things separated - incoming parsed message, outgoing message, user
specified data etc.)
thanks!
erik
_______________________________________________
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.
