The xMatters Health Monitor sends error and warning messages to an email address specified in the Global Configuration settings. This article identifies some of the common Health Monitor messages, and explains how to resolve the identified issues.
This article has been expanded and incorporated in the xMatters installation and administration guide.
This error message usually results when a message is sent to a component (i.e., a Device Engine) for processing, but no acknowledgment is ever received indicating that the component was able to process the message. As this can result from a number of situations, the only recourse is usually to examine the Node logs.
This error message usually results when the Node attempts to send a message to a component (i.e., a Device Engine) for processing, but is unable to locate the target component, or the target component does not exist. If you receive this error message, you can try the following solutions:
- Ensure that the target component exists, and is currently running. You can view component status in the web user interface, on the Nodes and Device Engines page.
- Ensure that the target component is not overloaded; this error message can also be generated if the Device Engine is attempting to process too many messages.
JDN-1307 Originally created by Don Clark