Unified Logging for network

[John Rose]

On Nov 2, 2020, at 4:39 AM, Leo Korinth <leo.korinth at oracle.com> wrote:
> 
> 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.

I think we have re-invented Heisenlogs here.  If there were a
lower-latency, more stable backing store for log output,
as compared to disk files, then *that* would be a good RFE,
but I agree with Thomas and Leo here that plumbing low-level
log output straight up to a TCP (!) point is asking for trouble.
Specifically, it’s asking for a new class of disruptive and
unpredictable observation effects.

I think we should inquire what are the best-of-breed log data
collectors (that solve for observation effects) and make sure
that the JVM has a way to hook up to them—locally.  And if
those collectors just watch files, then we are done, I guess,
although surely there is some fit and finish to add.

> 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).