Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.8.11, 1.8.14, 1.9.91
-
Component/s: Reports/Statsd, Web UI - Reporting
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Environment:Linux, probably all
Description
In the SQL query in NodeAvailabilityReport.jrxml
node_outages.avail_total is being calculated as total number of seconds in the period being included (e.g., 604800 for a 7 day period)
outage_seconds is being calculated as the sum of individual outages, not taking into account the number of interfaces in each node.
This causes the outage time (and outage percentage) to be effectively multiplied by the numeber of interfaces in a node with multiple interfaces monitored.
I saw this on 1.8.11, but looked at fisheye, and the query remains the same.
node_outages.avail_total is being calculated as total number of seconds in the period being included (e.g., 604800 for a 7 day period)
outage_seconds is being calculated as the sum of individual outages, not taking into account the number of interfaces in each node.
This causes the outage time (and outage percentage) to be effectively multiplied by the numeber of interfaces in a node with multiple interfaces monitored.
I saw this on 1.8.11, but looked at fisheye, and the query remains the same.
The query should only be looking at the nodeDown events. Only node level outages should be counted. We aren't counting the interface level outages. So that shouldn't be a problem.