Sergey Yedrikov
Sergey Yedrikov
Just leaving a comment here that I started working on a new syslog sink, with https://github.com/vectordotdev/vector/pull/7106 as inspiration.
> > Just leaving a comment here that I started working on a new syslog sink, with #7106 as inspiration. > > Great! Just a note that we would like...
On a second thought, I'm not sure this is an AWS SDK issue necessarily. Consider this test snippet, which is supposed to fail a create_log_group() call at different log levels:...
I'm adding two new log options to podman CLI in my POC, passed as part of --log-opt: policy=backpressure|drop|ignore|passthrough Peter has covered the first three, passthrough is current behavior with unrestricted...
@rhatdan A WIP PR: https://github.com/containers/conmon/pull/92 Another PR in libpod for the CLI changes: https://github.com/containers/libpod/pull/4663
> what happens in the back-pressure case? When over output quota in a particular time period, container log writes will block on a pipe that conmon reads from until the...
> > > what happens in the back-pressure case? > > > > > > When over output quota in a particular time period, container log writes will block on...
> @syedriko I mean a PR to containers/common to add these limits. @rhatdan Could you give me a bit more details? I'm new to the containers code base and I'm...
>What motivation do you have for looking for this behavior? It would simplify what a downstream log processor like Fluentd needs to do to assemble complete log lines, from a...