Show when failure FIRST started not just when alert triggered | Archive

thanh_rodke · 2014-04-10T00:00:00Z

Scenario say that you have a datasource that polls every two minutes, and you set the alert to go after five intervals then the condition starts at 10AM, and so the alert would fire at 10:10AM so the condition occurs for ten minutes (five intervals of two minutes) and the alert fires the alert email arrives as expected at maybe 10:11 or 10:12 AM the alert says that the start time is 10:10 AM and the duration is 0h 0m, but the error actually started ten minutes ago, and has been going on for ten minutes Business case: we have lots of items that we need historical data on, but are not necessarily "drop right now and fix" items, so we may not alert for 10-30 minutes, some even longer this also has put a huge dampener on false positives having accurate times listed in the initial and subsequent alerts can be helpful for remediation, and you don't have to calculate each time how far back to start digging in the server logs based upon that particular alert it's more difficult to determine if you have misconfigured a datasource (quantities of alerts all of a sudden go up, but you can tell how many intervals or how much time has elapsed since the error actually began) it's just inaccurate and can be confusing to to our MSP customers

MoreDiscussions

Show when failure FIRST started not just when alert triggered | Archive | LogicMonitor Community