I noticed looking through the code that it looks like the error file routine in omelasticsearch is not tied into the stats system - we use impstats to monitor our rsyslog pipelines, and having a counter for write errors would be super useful.
I've submitted a PR to add the counter: https://github.com/rsyslog/rsyslog/pull/1331 Cheers, Brian On Thu, Dec 15, 2016 at 7:58 AM mostolog--- via rsyslog < rsyslog@lists.adiscon.com> wrote: > Solved using json template (code blindness). > > Is there any way to set fields and use them (like @timestamp) but not > indexing them on elastic? (hidden fields) > > Just tried with @timestamp, but it's being indexed :( > > > > El 15/12/16 a las 12:32, mosto...@gmail.com escribió: > > Hi > > > > > > At this moment we are frowarding RELP messages to Elasticsearch using > > omelasticsearch plugin, but sadly message appears as json instead of > > storing each properties. eg: message is { "app": "app1"... instead of > > indexed document having a app property. > > > > Should we specify an especial param on rsyslog, a setting on elastic...? > > > > Regards > > _______________________________________________ > 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. > _______________________________________________ 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.
