[esb-issues] [JBoss JIRA] Created: (JBESB-2501) Monitoring details needed on individual messages

Monitoring details needed on individual messages ------------------------------------------------ Key: JBESB-2501 URL: https://jira.jboss.org/jira/browse/JBESB-2501 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.5 Reporter: Tom Cunningham Assignee: Tom Cunningham We need to expand support for monitoring to include some sort of trace on an individual message - which is a feature we've talked about for some time. The first level of this support would probably be being able to track a "tracer bullet" message through header id's and keeping statistics on that message. "Governance: tracebility of messages, message header logging, draw a graph to show each place a message visits, trace back to a failure where did the message visit prior to that failure, we are currently using JON but only seeing the aggregate numbers, not actually seeing which messages impacted the failing services. Record the message headers to see the back-trail. and -- The msg count/failure count isn't valuable, monitoring of the log (via JON alert based on ERROR or FATAL) is more valuable -- Start & stop individual listeners vs the whole esb archive. -- SLAs are important, hard to define in JON like if this service has a response time slower than X then alert. The current response time is an average, we want to look for discreet response times (avg at 5 secs but 1 message at 20 secs then alert)" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira