It depends, on how those notifications are generated. 1) If you produce JMX notifications from an MBean, and the ActiveAlarmTable subscribes for them, you need to produce special notification types that carry severity. The easiest way to do this is to use the AlarmManager helper class: http://wiki.jboss.org/wiki/Wiki.jsp?page=AlarmManager. This is most useful if you want to indicate conditions that "clear" themselves out (e.g. memory low, memory ok). Or else produce directly org.jboss.monitor.alarm.AlarmNotification that carry the severity.
2) If you want to present ordinary notifications as alarms, you need to map them to AlarmNotifications. You could use the ScriptingListener for this: http://wiki.jboss.org/wiki/Wiki.jsp?page=ScriptingListener 3) If those are log4j messages, then you can't, the mapping is fixed, see http://wiki.jboss.org/wiki/Wiki.jsp?page=JMXNotificationAppender I guess if there is enough demand I could add some basic mapping mechanism in the AlarmTableService itself, e.g. notification type X --> CRITICAl. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920441#3920441 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920441 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
