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
On 08/28/2018 06:56 PM, David Lang wrote:
On Tue, 28 Aug 2018, Rich Megginson wrote:
On 08/28/2018 06:20 PM, David Lang wrote:
On Tue, 28 Aug 2018, Rich Megginson via rsyslog wrote:
As part of the fix for https://github.com/rsyslog/rsyslog/pull/2962
I've added handling for error 429 Busy.
On Tue, 28 Aug 2018, Rich Megginson wrote:
On 08/28/2018 06:20 PM, David Lang wrote:
On Tue, 28 Aug 2018, Rich Megginson via rsyslog wrote:
As part of the fix for https://github.com/rsyslog/rsyslog/pull/2962 I've
added handling for error 429 Busy. I've seen this most commonly with
large
On 08/28/2018 06:20 PM, David Lang wrote:
On Tue, 28 Aug 2018, Rich Megginson via rsyslog wrote:
As part of the fix for https://github.com/rsyslog/rsyslog/pull/2962
I've added handling for error 429 Busy. I've seen this most commonly
with large Kubernetes clusters where if you have hundreds
On 08/28/2018 06:23 PM, David Lang wrote:
As we are looking at managing and securing our k8s install, we are
finding that getting a token out of the pod/container runing the
management processes is non-trivial, especially to get it onto a
separate log server.
would it be possible to add
As we are looking at managing and securing our k8s install, we are finding that
getting a token out of the pod/container runing the management processes is
non-trivial, especially to get it onto a separate log server.
would it be possible to add client cert auth to the token option? This is
On Tue, 28 Aug 2018, Rich Megginson via rsyslog wrote:
As part of the fix for https://github.com/rsyslog/rsyslog/pull/2962 I've
added handling for error 429 Busy. I've seen this most commonly with
large Kubernetes clusters where if you have hundreds of nodes, all with
open connections to the
As part of the fix for https://github.com/rsyslog/rsyslog/pull/2962 I've
added handling for error 429 Busy. I've seen this most commonly with
large Kubernetes clusters where if you have hundreds of nodes, all with
open connections to the Kubernetes API service, the service will
eventually hit
8 matches
Mail list logo
