we would be open to a patch for a flag that dropped the offending message and
kept going (see my other message about batch handling) but not to just ignore
the message and retry.
David Lang
On Wed, 6 Dec 2023, Peter Portante via rsyslog wrote:
Hello Rsyslog People!
I have been working with the Ansible team on a use case of rsyslogd
forwarding logs to Splunk via omhttp.
Is there anyway to get movement on a fix for
https://github.com/rsyslog/rsyslog/issues/4348? Would the community be up
for a patch that allowed for a flag to change the current omhttp behavior
of stopping on a 4xx error into one where 4xx errors are logged and then
continues sending?
Thanks for considering!
-Peter
_______________________________________________
rsyslog mailing list
https://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
https://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.
