On 08/28/2018 08:20 PM, David Lang wrote:
On Tue, 28 Aug 2018, Rich Megginson wrote:
It would have to be done inside the module, rsyslog has back-off capabilities,
but only when the entire pipeline is suspended.
Another option is to handle 429 in mmkubernetes similar to how it is handled in omelasticsearch - resubmit the record back to the beginning of the processing pipeline, for cases when you
absolutely must have the metadata associated with the record, and you cannot accept records without the appropriate metadata.
you don't want to do that within the module (you will HAMMER the API server
with requests)
you can't resubmit the log back to the start of processing as other actions may
have already taken place.
If you absolutly don't want to process any messages without the metadata, all
you can do is to suspend if you get a 429
I've updated the PR https://github.com/rsyslog/rsyslog/pull/2962
By default, if it gets a 429 response, it will continue processing the records without the additional metadata, and retry the connection every 5 seconds. There is a new config param
busyretryinterval to control this time. If you set it to 0, then the plugin will return an error when gets a 429.
This update also adds support for client cert auth, and per-instance/per-action
statistics. You should be able to use this PR with multiple different
Kubernetes clusters.
David Lang
_______________________________________________
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.
