Forum Discussion

Anonymous's avatar
Anonymous
2 years ago

6 polls, 5 poll cycles, or 12 minutes

Alright, take a look at this. The poll rate for this DS is 2 minutes. What is the trigger window? Assume all the criteria is met starting a 1:59 PM and 30 seconds (between polls). When will the alert be triggered? It’s actually 10 minutes (2:10 PM, +/- a couple seconds for collector task queue delay and assuming original scheduling at the top of the hour).

Do you know why? Why does it say 12 minutes? Why not 10? Is this behavior different than regular alert trigger intervals?

  • Hmm, I had to write it out to wrap my head around on this one :)

    13:58:00 - checked, no issues
    13:59:30 - condition matches
    14:00:00 - 1st poll /w match
    14:02:00 - 2nd poll /w match
    14:04:00 - 3rd poll /w match
    14:06:00 - 4th poll /w match
    14:08:00 - 5th poll /w match
    14:10:00 - 6th poll /w match… ALERT!
    Diff: 10m 30s

    But technically it can be anywhere between 10m 0s to 11m 59s depending on the timing. I assume they are just taking the Cycle * Polls (2 * 6) = 12. I guess it might be more confusing for users to see 10min or 11min even if those are more likely?

    13:58:00 - checked, no issues
    13:58:01 - condition matches
    14:00:00 - 1st poll...
    14:10:00 - 6th poll (alert)
    Diff: 11m 59s

    13:58:00 - checked, no issues
    14:00:00 - 1st poll and condition matches...
    14:10:00 - 6th poll (alert)
    Diff: 10m 00s

  • Anonymous's avatar
    Anonymous

    Something else to think about, I'm not asking how long the problem would exist before the alert is opened. I'm asking what the configured window is. The difference is in how it matches up to a customer's requirements. If they say I want an alert when it's been highly utilized for 10 minutes or more, what value do you put here? If you put five, it will say 10 minutes. However, in many cases, that would lead to alerts in less than 10 minutes.

  • Hmm, I had to write it out to wrap my head around on this one :)

    13:58:00 - checked, no issues
    13:59:30 - condition matches
    14:00:00 - 1st poll /w match
    14:02:00 - 2nd poll /w match
    14:04:00 - 3rd poll /w match
    14:06:00 - 4th poll /w match
    14:08:00 - 5th poll /w match
    14:10:00 - 6th poll /w match… ALERT!
    Diff: 10m 30s

    But technically it can be anywhere between 10m 0s to 11m 59s depending on the timing. I assume they are just taking the Cycle * Polls (2 * 6) = 12. I guess it might be more confusing for users to see 10min or 11min even if those are more likely?

    13:58:00 - checked, no issues
    13:58:01 - condition matches
    14:00:00 - 1st poll...
    14:10:00 - 6th poll (alert)
    Diff: 11m 59s

    13:58:00 - checked, no issues
    14:00:00 - 1st poll and condition matches...
    14:10:00 - 6th poll (alert)
    Diff: 10m 00s