ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportMonitoring event vs log4j2

Post new topicReply to topic
Monitoring event vs log4j2 View previous topic :: View next topic
Author Message
KIT_INC
PostPosted: Thu Feb 22, 2018 6:20 am Post subject: Monitoring event vs log4j2 Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 549

We are running IIB 10 on AIX. Our developers are using log4j2 extensively. For example, logging before and after HTTP requests. We feel that these inline calls increase the chance of failure and also impact performance. We have flows that uses 15+ additional instances for throughput requirement. We think that MB event monitoring can do the kind of logging they need and like to see if that is a better option. We are looking for some experience if some one has dome the switch before ? or if there any paper on using monitoring vs Log4j2 for logging messages through the message flow.
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Feb 22, 2018 6:41 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25318
Location: Ohio, USA

Not done the switch, but we do logging (audit & BAM) using event messages because log4j sucks under load; the gismo reading the event messages uses javax.util.logging.

Never heard of log4j2 until someone mentioned it in here a while back, never used it, can't comment on it except that all Java is a dark magic which will one day destroy the world.

I personally also like the ability to add additional logging to flows by administratively adding a new monitoring profile to the flow rather than adding more code to the flow and going through the deployment process. Developers (Java and otherwise) consider this code-free logging witchcraft and have put in the request forms for enough wood to burn me at the stake. Having seen the operational budget for 2018 I'm confident I just need to continue to dodge the holy water occasionally thrown at me.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportMonitoring event vs log4j2
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.