Aggregated Status (APS1)

Description

This probe monitors a list of other probes. When the number of monitored probes in a non-OK state reaches the Warning or Critical Level defined the Aggregated Probe state changes to Warning or Critical, respectively. The monitored probes can be from any SOP of the cluster and should usually be of the same type.

Release notes

Show release notes
Version 1.1 - Early deployment
  • Feature: Nested aggregated probes (M0005467)
  • Dependency:
    • (on BMS, please contact ESCAUX) escaux-smp-base >= 1.8
    • (on BMS, please contact ESCAUX) escaux-nagios-config >= 1.7
    • SMP >= 4.9 (optional: to be able to disable probe notifications)

Version 1.0 - Early deployment
  • Feature: Initial version (M0003312)
  • Dependency:
    • (on BMS, please contact ESCAUX) escaux-smp-base >= 1.8
    • (on BMS, please contact ESCAUX) escaux-nagios-config >= 1.7
    • SMP >= 4.9 (optional: to be able to disable probe notifications)

Resource configuration interface

GUI unavailable.

Resource configuration parameters

  • Warning level: Number of monitored probes in non-OK state needed to set Warning state
  • Critical level: Number of monitored probes in non-OK state needed to set Critical state
  • Monitored probes: Select the probes from the cluster which should be monitored.

Setting notifications to "None" or "Only Critical" on each monitored probe is recommended (needs SMP >= 4.9).

Limitations

  • When used on a cluster of SOPs, this probe is linked to the cluster master SOPkey. To see the probe on the BMS, the monitoring of the cluster should be activated (in Cluster Configuration).

  • This probe depends on some BMS components, ask Escaux to do the upgrade if needed.

Performance graphs

This probe does not generate any performance graphs.

Alarms

This probe can report following alarm states:

  • CRITICAL: the number of monitored probes in non-OK state reached the defined critical level
  • WARNING: the number of monitored probes in non-OK state reached the defined warning level

Possible causes

Depends on the monitored probes.

Possible consequences

Depends on the monitored probes.

Possible actions

Depends on the monitored probes.

Example of use: Monitoring a bundle of PRI's on several SOP's of the same cluster

  • Create a ZPU1 probe for each PRI on each SOP
    • Set notifications to "Only critical"
  • Create an APS1 probe on the cluster
    • Select all the ZPU1 probes in monitored probes
    • Choose a warning level (ex: total number of PRI's - 1) and a critical level (ex: total number of PRI's)

The APS1 probe will return a status and notifications based on all PRI's usage. Notifications from individual PRI's will only be sent in the case of a connectivity problem.
Copyright © Escaux SA