Monitoring systems typically track the health of individual elements or nodes. Each element represents a specific piece of infrastructure — such as a router, firewall, server, network interface — or a software component, like a SQL database, Active Directory server, or DNS service.
However, a single service usually depends on multiple elements working properly. For example, a hosted database service may rely on a healthy server, network connection, DNS resolution, and functioning database software to be considered Up.
Nextian RMM calculates an aggregate service status based on the individual statuses of the elements required to support that service. It updates service (operational) status (Up, Down, Warning) and availability statistics in Salesforce based on the following:
- Service Elements: Elements that make up a service, retrieved from Salesforce. Only elements that are monitored are considered.
- Individual Element Statuses: Retrieved from the source NMS for each element obtained in step 1.
- Operational Status Rules: Rules that determine the overall service status based on the statuses of all associated elements. Each service has its own rule, defined in Salesforce in the Operational Status Rules field.
A simple example rule that defines a service as Up only if all related elements are also Up looks like this:
simpleCondition( [status: UP]
Detailed information about the Operational Status Rules syntax is provided here.
