While somewhat old thread, I beg to disagree. SLAs might very well include situations where business transactions are part of it. In integrations / message delivery business (be it SWIFT messages, EDI messages, invoices, orders etc) the basics of SLA are usually built on certain assumptions:
- All messages that have been sent, are processed within a certain timeframe (this could be something like 30 mins to 24 hours).
- No messages should be lost
This means one needs to create a single environment to monitor everything, both the business transactions (to verify that everything we've received has been processed and something hasn't got stuck to some service, because of deadlock or other event), and that the services are up. Traditional monitoring of API-speed could very well be quite irrelevant (these messages are often sent through old-fashioned-gateways, such as SFTP/FTP servers) as it's not interesting to any party. In these cases having just one monitoring tool would be quite important. Sending events from the BAM to the RHQ is quite "must-have" feature in my opinion. RHQ can already read Events, so I don't see any technical limitation from the RHQ's part, it's just that someone has to create that integration layer (RHQ plugin, or BAM sending events to RHQ).
I don't believe the original post was stating these requirements could be provided by a single environment, just that there was a different focus, and that the first (i.e. SLA) could be achieved using a more traditional management system approach.
However the scenario you mention can be handled in one environment, using rtgov to monitor the business level requirements and report any issues to a management system via JMX - and then have that management system also monitor the availability of those services.