Unified Logging for network

[Leo Korinth]

I think it is a mistake. Making UL easy to use over network will make people use it (over network). It will have bad latency and will transfer an unstable log format. If some important data is missing from JFR, would it not be better to add new JFR events? If you need it for debug reasons, you could just pipe stdout through netcat (I guess).

Thanks,
Leo

On 02/11/2020 12:20, Yasumasa Suenaga 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.