Is writing to a message queue a good idea?

I am currently facing the problem of combining multiple log files from a distributed system.

But since most applications are Java applications that use both log4j and all of them use JMS, I thought about registering directly in the message queue instead of copying individual log files.

Is this a good idea or could it be something like that?

+5
source share
3 answers

A few ideas:

  • performance has already been mentioned - the inclusion of detailed debugging information may not be possible in a production environment (if it turns out that you need to track a deeply hidden error),
  • log4j roll-over , , ,
  • / ( , ),
  • , , ;— , log4j - ,
  • ( ) .
+2

, . , JMS, log4j. log4j, , JMS.

+1
  • Log4j (in your case) or preferably NXLog ( http://nxlog-ce.sourceforge.net/ )
  • Some log shipping agent (nxlog.exe) sends log files to
  • ELK stack (Elasticsearch, Logstash and Kibana) that you run as docker containers

https://www.elastic.co/webinars/introduction-elk-stack .

0
source

All Articles