Joe,
The webMethods Manager may do all that you wish. See below - took the reqs in your request and provided answers. It is new and you will need to contact your local sales team for release and pricing.
You might also want to search the webMethods site for pages and articles on OMI - Open Management Interface. While you could go down to the older APIs, the OMI may be the better place to start.
Mark Thomsen
Alodar Systems, Inc.
Q: …monitor things such as internal WM queue-depths…
A: Yes. Queue length in docs and in bytes, and queue operations.
Q: …the health of adapters, etc.
A: Yes. The health of running parts as well as some of the logical parts - health of a business process step, of an integration component, of an IS service.
Q: …verify the state of our production brokers, queues, adapters, etc.
A: Yes. The operational status. The current metrics. The connectivity of the components (e.g., which broker an adapter is connected to, which adapter an integration component runs on, which integration component a business process step is implemented with, which step follows another step in a business process, …).
Q: Not monitoring BY the broker, but monitoring OF the broker (and its components).
A: Yes. This is why you would want to go with the OMI and Manager. It monitors the enterprise and B2B components, retaining things like there should be a broker server on a certain host and while it is down and not responding, you still see it, in a down state.
Q: …alarms (or e-mails, etc.) sent out, if a bad condition is detected.
A: Yes. They even built in a web server alerting feature.