You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2018/11/06 15:43:29 UTC

[GitHub] csquire commented on issue #2992: PoC for log library surface reduction (2991)

csquire commented on issue #2992: PoC for log library surface reduction (2991)
URL: https://github.com/apache/cloudstack/pull/2992#issuecomment-436298914
 
 
   Why not use SLF4J instead of reinventing your own facade?
   As a developer of an internal plugin, I find it frustrating to be forced into using limited one-off implementations. In particular, I am sending managment server logs to ELK in a JSON format. With SLF4J, Logback with the [Logstash Logback Encoder](https://github.com/logstash/logstash-logback-encoder), I can use Markers to add event-specific custom fields wherever I want. This is very useful for searching and filtering logs in ELK, not to mention the potential that exists for visualization of log events based on custom JSON fields. I assume a similar thing can be done with SLF4J and log4j2, but I have not reasearched it much. But, if Cloudstack uses a homegrown facade, it will not have a full logging feature set available.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services