2 Oct 2008 10:27
Alert Pattern - why does this not match
Marc Haber <mh+smokeping-users <at> zugschlus.de>
2008-10-02 08:27:12 GMT
2008-10-02 08:27:12 GMT
Hi, this is from a SmokeAlert foo cleared e-mail created by smokeping 2.0.9 (from Debian stable): Pattern ------- ==0%,>0%,*12*,>0%,*12*,>0%,*28* Data (old --> now) ------------------ loss: 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 5%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0%, 0% rtt: 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms, 1ms The loss data row still has three >0% items, and the trailing *28* should indicate that smokeping shouldn't care about whether the last non-zero data point is last or not. But the alert is still raised when the last data point is non-zero and cleared when the last data point becomes zero again. In the mean time, I have modified the pattern to read ==0%,>0%,*12*,>0%,*12*,>0%,*28*,>=0% and we'll see whether that helps. What have I been doing wrong, and is my workaround the desired one? Greetings(Continue reading)
RSS Feed