search

vladimirvivien / jmx-logger

JMX Logger for JUL and Log4J (old project & little support)
3 stars 2 forks source link

Make the jmx notification configurable #6

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What is the expected output? What do you see instead?
I think there needs to be more flexibility in the notification properties.

1. I would like to turn on and off properties displayed in the console like 
source and destination. here they always present the same data.

2. I would like the formatted message from the layout to appear exactly as 
it does in all other regular appenders. Here I feel that the appender uses 
the layout in more than one place.

3. Generally speaking, if my layout contains every thing I want including 
logger name, timestamp etc, I would expect to have the ability to display 
only the formatted message. I control the formatted message via Layout.

What version of the product are you using? On what operating system?

0.1.0, windows and Linux

Original issue reported on code.google.com by yairogen on 15 Oct 2009 at 9:17

GoogleCodeExporter commented 8 years ago 
Decided not to take action on these issues at this time.  Here are the reasons:

Issue 1. I would like to turn on and off properties displayed in the console 
like 
source and destination. here they always present the same data.
==> Workaround <== JmxHandler today grabs all possible event fields and place it
inside the JMX notification.  The formatted message is part of the payload 
pushed to
the JMX event bus.  A tool or code can easily pull out the data in the 
configured format.

Issue 2. I would like the formatted message from the layout to appear exactly 
as 
it does in all other regular appenders. Here I feel that the appender uses 
the layout in more than one place.
==> Workaround <== JmxLogger's log4j Appender uses whatever Layout specified 
when you
set it up.  The formatted message is part of the larger notification payload.  
Again,
you would need a view or easily write code to pull out the necessary formatted 
event.

Issue 3. Generally speaking, if my layout contains everything I want including 
logger name, timestamp etc, I would expect to have the ability to display 
only the formatted message. I control the formatted message via Layout.
==> Workaround <== I agree.  JmxLogger keeps the formatted message as part of 
the
notification payload.  That formatted message can easily be extracted
(programmatically) or via a tool (maybe that's the next project, stay tuned). 
JmxLogger provides appender/handler that pushes the log event as JMX 
notification. 

Future version may revisit some of the issues.  However for now, I feel that
JmxLogger has met its minimum requirements which is to broadcast event logs as 
JMX
notifications.  For event extraction and presentation features, a new project 
may be
more suited to handle these features.

Original comment by vladimir...@gmail.com on 19 Oct 2009 at 7:28