Unified Logging for network

[Yasumasa Suenaga]

Hi Thomas, John,

I'd like JVM to provide "sink mechanism" for UL other than file/stdout/stderr in a word.
stdout/err might be mixed application log (other than UL output). If we use combination of file and other tools (e.g. syslogd), we also need to consider them.

JEP 158 (Unified JVM Logging) mentions syslog, Windows Event Viewer, socket could be added as UL backend in future possible extensions. I think this proposal is not specialized to some tools because JVM would just send UL as plain text to some consumer, and also it is evolutional work for JEP 158.


On 2020/11/08 6:13, John Rose wrote:
> On Nov 7, 2020, at 10:52 AM, Thomas Stüfe <thomas.stuefe at gmail.com <mailto:thomas.stuefe at gmail.com>> wrote:
>>
>> So if done right, this gets a bit complex. And I think it is worth doing
>> right. Therefore I think, like John and Robbin, that before reinventing
>> this wheel we should check if there are standard tools which do all this
>> already.
> 
> I’d go a little farther:  Surely such a tool exists, because
> the JVM is not unique as an event source.  Even if exactly
> the right tool (a “UL shipper” in the gist) does not exist,
> it does not follow that we should create and maintain
> such a thing.  That’s the job of cloud infrastructure
> engineers, who do something different from JVM
> engineers.  If the JVM puts special requirements on
> such a tool, then we need to work with one or more
> “UL shipper” tool providers to meet in the middle,
> not go off and build our own.
> 
> Thanks for the good discussion!
> 
> — John