Hey Jared,
That error message *is* pretty ugly. I've improved it somewhat:
lappytop test threshold of 3500000 exceeded: current value 3682304.00
lappytop test threshold restored current value: 3158016.00
lappytop test threshold of 3000000 not met: current value 2629632.00
The following change to the 0.22 branch fixes the check against minimum
thresholds:
http://dev.zenoss.org/trac/changeset/2542
-Eric
Jared Meeker wrote:
Has anyone else had a problem with custom thresholds working? I've been
successful with creating them and having the lines show upon the graphs,
however, I have run into two problems.
1. Thresholds with only a min defined never generate events (no event in the app or via email)
2. Thresholds with a min AND a max defined generate events for both cases, but if the polled value is less than the min, then the message looks something like this (min=9, max=11):
"[servername] [threshold name] threshold of 2 exceeded: current value 10.00"
Also, thresholds with only a max defined work as expected.
Thanks in advance.
- Jared
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
