9 years ago
No data threshold
Hi,
I love the idea behind the "no data" warning, but it's missing one thing that I think would help make it a little more friendly. We have a few devices that have spotty collection reliabi...
Hello Everyone,
I just saw this and wanted to confirm what Mike was referring to. If I have a datapoint, such as CPUBusyPercent, that has an "Alert trigger interval (consecutive polls)" set to 4 AND I set "If there is no data for this datapoint:" to trigger an alert, the No Data alert would trigger after 4 consecutive polls, just as the regular thresholds would that are set on the datapoint.
If you wanted to extend the time to trigger a No Data alert, or have a specific amount of consecutive polls for No Data, you can always set the No Data alert on a datapoint that has no threshold, adjust the "Alert trigger interval (consecutive polls)" to what you deem appropriate, and it will respect the amount of consecutive polls set before triggering a No Data alert.
For the most part this can be any datapoint you choose on the datasource, as usually when you are getting No Data, it is not just that one specific datapoint, it is usually the whole protocol not responding (WMI, SNMP, JDBC, etc.).
Hope that clears this up, let us know if you have any other questions related to this.