Hi.
Am 16.08.2018 um 16:27 schrieb Rich Megginson:
> On 08/16/2018 05:42 AM, Aleksandar Lazic wrote:
>> Am 16.08.2018 um 12:48 schrieb Aleksandar Kostadinov:
>>> Might be real nice to allow pod to request sockets created where different
>>> log
>>> streams can be sent to central logging without e
On 08/16/2018 05:42 AM, Aleksandar Lazic wrote:
Am 16.08.2018 um 12:48 schrieb Aleksandar Kostadinov:
Might be real nice to allow pod to request sockets created where different log
streams can be sent to central logging without extra containers in the pod.
You can run socklog/fluentbit/... in t
Am 16.08.2018 um 12:48 schrieb Aleksandar Kostadinov:
> Might be real nice to allow pod to request sockets created where different log
> streams can be sent to central logging without extra containers in the pod.
You can run socklog/fluentbit/... in the background to handle the logging and
your ap
Might be real nice to allow pod to request sockets created where
different log streams can be sent to central logging without extra
containers in the pod.
Jeff Cantrill wrote on 08/15/18 16:50:
The recommended options with the current log stack are either to
reconfigure your log to send to std
The recommended options with the current log stack are either to
reconfigure your log to send to stdout or add a sidecar container that is
capable of tailing the log in question which would write it to stdout and
ultimately read by fluentd.
On Wed, Aug 15, 2018 at 2:47 AM, Leo David wrote:
> Hi
Hi Everyone,
I have logging with fluentd / elasticsearch at cluster level running
fine, everything works as expected.
I have an issue though...
What would it be the procedure to add some custom log files from different
containers ( logs that are not shown in stdout ) to be delivered to
elasticseac
