Background:
Using NPM v12.1
- We have an alert that triggers off of this condition:
Volume -> "Disk Seconds Per Transfer" >= 0.20
- In the Orion UI under Settings -> Orion Polling settings it has these two settings for polling Volume data:
"DEFAULT VOLUME POLL INTERVAL"
"DEFAULT VOLUME STATISTICS POLL INTERVAL"
Question: When the alerting rule runs and uses this metric to alert on, is the Volume -> "Disk Seconds Per Transfer" triggering off of the data collected during the Default polling interval (the "most up to date" data) , or the statistics interval ("summarized/calculated" data)?
Note: In the Orion UI, there is a resource for "Avg Disk Seconds per transfer" which I believe is the summarized data, and I can't seem to find a way to chart the raw data collected, so it seems to reason the alert can *only* trigger off of summarized data as this may only exist as a summarized metric (it seems to be a summation of reads/writes, but I'm not sure if Orion is doing this calculation or if it's occurring on the Windows system being polled and Orion pulls the metric at the polling interval and not the statistics interval), however, in my alerting rule I have it set to report on the value it alerted on via this text: "${NodeName} Disk Transfer Latency is ${DiskTransfer}", and it seems that this variable may be pointing to non-summarized data (or maybe there is rounding occurring somewhere)?