Triggers sent multiple Email alerts within given period T (sec)
Monitored systems OS: Win Profess
Item: system.cpu.util[,system,avg1]
Trigger: Host1:system.cpu.util[,system,avg1].avg(300)>90
What I get after upgrading 1.4 to 1.4.1 from Email Alerts
!CPU Utilization is High, avg in 300 sec > 90% on Host1 <202.xx.xx.xx> on 2007.07.05 08:09:52. Last recorded value is 94.22 %.
!CPU Utilization is High, avg in 300 sec > 90% on Host1 <202.xx.xx.xx> on 2007.07.05 08:09:34. Last recorded value is 94.62 %.
What I get for 1.4 (for 2 weeks, such daily alerts are fine)
!CPU Utilization is High, avg in 300 sec > 90% on Host1 <202.xx.xx.xx> on 2007.07.02 06:17:15. Last recorded value is 98.97 %.
!CPU Utilization is High, avg in 300 sec > 90% on Host1 <202.xx.xx.xx> on 2007.07.02 06:07:38. Last recorded value is 91.13 %.
Server System: CentOS, Mysql 4.x.x
Monitored systems OS: Win Profess
Item: system.cpu.util[,system,avg1]
Trigger: Host1:system.cpu.util[,system,avg1].avg(300)>90
What I get after upgrading 1.4 to 1.4.1 from Email Alerts
!CPU Utilization is High, avg in 300 sec > 90% on Host1 <202.xx.xx.xx> on 2007.07.05 08:09:52. Last recorded value is 94.22 %.
!CPU Utilization is High, avg in 300 sec > 90% on Host1 <202.xx.xx.xx> on 2007.07.05 08:09:34. Last recorded value is 94.62 %.
What I get for 1.4 (for 2 weeks, such daily alerts are fine)
!CPU Utilization is High, avg in 300 sec > 90% on Host1 <202.xx.xx.xx> on 2007.07.02 06:17:15. Last recorded value is 98.97 %.
!CPU Utilization is High, avg in 300 sec > 90% on Host1 <202.xx.xx.xx> on 2007.07.02 06:07:38. Last recorded value is 91.13 %.
Server System: CentOS, Mysql 4.x.x
Comment