Monitoring the Microsoft Exchange Hub Transport Server
eG Enterprise provides an Microsoft Exchange Hub Transport model that monitors the internal health of the Hub Transport server.
Figure 1 : Layer model of the Microsoft Exchange Hub Transport server
The tests mapped to each layer report critical statistics that reveal the following:
- Is the server experiencing processing bottlenecks? Are there any lengthy message queues on the server? If so, which ones?
- How effective is the Recipient filter agent? How many requests per second were rejected by the Recipient Lookup and Recipient Block List data sources?
- How successful is the Sender Filter agent in evaluating and filtering out "suspect" senders?
- Is the Sender ID agent efficient?
- Has the Hub Transport server experienced latencies while connecting to the Exchange store? Which store interface can this delay be attributed to?
- How many messages are available in the delivery queue? Is the number very high?
- Do too many messages exist in the retry queue?
- Are too many messages awaiting delivery to an external recipient?
- Have messages been queued in the Unreachable queue?
- Does the poison queue contain messages?
- Which receive connector is overloaded with data and messages?