Table of Contents |
---|
Grouped Availability Report
New in version 3.1.10
opreports_availability_average_packetloss
A new configuration setting 'opreports_availability_average_packetloss' in /path/to/omk/conf/opCommon.nmis, controls whether the previous 'Packet Loss %' (now renamed 'Count Packet Loss %' ) or 'Average Packet Loss %' is displayed in this report for each group.
'opreports_availability_average_packetloss' => 'false' , the default setting, causes 'Count Packet Loss %' to be displayed: This can be interpreted as 'percentage of readings with some amount of packet loss (Count readings with any packet loss / Number of readings)'.
'opreports_availability_average_packetloss' => 'true' causes 'Average Packet Loss %' to be displayed: This can be interpreted as ''Average Packet Loss (Sum of packets lost / Number of readings).
New in version 3.1.
...
5
opreports_availability_strict (default: true)
- if missing or 'true', then the normal behaviour for nodata-or-normal is used (ie. if reachability isn't present, it counts as nodata).
- no data = 'down' when opreports_availability_strict=true
- If set to 'false', then records with missing reachability but existing response time are fudged up so that the reachability = 100 (and loss = 0 if that's also missing) and therefore such a record does NOT count as nodata.
- no data = 'up' when opreports_availability_strict=false
In both cases, if reachability is missing but response time is present, a debug3 about the inconsistency is logged. This applies to both availability report data and availability report graphs.
New in version 3.1.4
Reachability Statistics
The Grouped Availability Report computes reachability statistics similar to the Node Availability Report, but devices are then categorised based on their overall availability metric; the report shows these results spread over various summary table sections (for HTML output) or work sheets (for XLSX output).
...
Both business days and business hour filtering are supported. The availability categories can be configured flexibly by adjusting thresholds and settings.
Total Availability
A combined total availability metric for all nodes is computed and presented in a summary section, and similar metrics and categorisation device counts for both grouping by Customer and Group (ie. NMIS configuration properties customer
and group
) are computed and presented. Finally the detailed availability stats are shown for all devices, in order of the devices' group memberships. Instead of determining an individual devices availability as the Node Availability Report does, the Grouped Availability Report is based on the overall availability metric and gives a summary of the availability of all the devices within a specific group. The summary section displays the number of devices within that group, the number customers within the group, the number of groups and the overall availability of them. The summary section will display devices with availability of 100%, 99 < 100%, 98 < 99%, and < 98% to easily understand if any group of devices has had unexpected downtime. The Grouped Availability Report also displays the Down%, Packet Loss %, No Data %, Uptime, and Downtime for a quick look at overall network health.
report_groupedavailability_levels
The Grouped Availability Report can be configured flexibly by adjusting the threshold settings of report_groupedavailability_levels in /usr/local/omk/conf/opCommon.nmis
Code Block |
---|
'report_groupedavailability_levels' => {
'default' => {
'good' => {
'color' => '',
'description' => '100%',
'threshold' => 100
},
'high' => {
'color' => '#ffff00',
'description' => '99 < 100%',
'threshold' => 99
},
'low' => {
'color' => '#ff8900',
'description' => '98 < 99%',
'threshold' => 98
},
'lowest' => {
'color' => '#ff0000',
'description' => '<98%',
'threshold' => -1
}
}
}, |
Example
A full example of a Grouped Availability Report with default settings can be downloaded and viewed HERE