Unified Logging for network

[Thomas Stüfe]

Hi Yasumasa,

one problem I see is that this could introduce a surprising amount of lag
into log() calls which do look inconspicuous, thereby distorting timing
behavior or even create timeout effects. We already have that problem now
to some degree when logging to network shares.

Another thing, log output can be very fine granular, which would create a
lot of network traffic.

Such an addition may also open some security questions.

>From a more philosophical standpoint, I like the "do one thing and do it
right" Unix way and this seems more like something an outside tool should
be doing. Which could also aggregate log output better. But I admit that
argument is weak.

Cheers, Thomas



On Mon, Nov 2, 2020 at 12:21 PM Yasumasa Suenaga <suenaga at oss.nttdata.com>
wrote:

> Hi all,
>
> We need to out UL to stdout and/or file. If we can out it to TCP socket, I
> think it is useful.
>
> For example, some system gather all logs to document oriented databases
> (e.g. Elasticsearch) and/or cloud monitoring platform (e.g. CloudWatch). If
> HotSpot can out UL to TCP socket, we can send all logs to them via TCP
> input plugin (Fluentd, Logstash).
>
> I think it is useful for container platform. What do you think?
> If it is worth to work, I will add CSR and JBS ticket, and also will
> create patch.
>