In fully correct way - it's only supported since 0.2.23, where you can specify thresholds like last() > 90 for 10 polls. However, you can get approximately the same result by giving average() > 90 for 10 polls.

Best regards,
Victor

1. If you monitor some DCI, you can define different thresholds with different events, for example one event if CPU utilization exceedes 90% for 1 minute, and other if it exceeds 90% for 10 minutes, and then process these events by sending appropriate emails.

I'm working on 0.2.23 release, most likely it will be out this weekend.

Best regards,
Victor

Is point one true for 0.2.23 only?

(offtopic: what's new about 0.2.23 release date?)

You can achieve notification escalation in various ways:

1. If you monitor some DCI, you can define different thresholds with different events, for example one event if CPU utilization exceedes 90% for 1 minute, and other if it exceeds 90% for 10 minutes, and then process these events by sending appropriate emails.
2. You can set timeouts on alarms, and process these timeout events. So, if problem occurs, you create alarm from an event, and if nobody acknowledges this alarm within given timeout period, you get another event which you may process and send another notification (and probably create another alarm with timeout, which will trigger third level of escalation, and so on).
3. If you just need to re-send notifications all the time to same destination for DCI threshold violations, you can simply set "repeat interval" in threshold configuration.

Best regards,
Victor