The critical state is still fairly new, so it may not be documented as
well as the others yet. In a custom TCP probe you can use DONE with the
CRIT status code, just like ALRM or WARN, to make the device go
critical. In a custom SNMP probe you can use "critical: " like "alarm:
" and "warning: " to do the same. Command line probes use the same
"critical: " syntax, where you can send the device into critical based
on a certain app's exit value.
The devices in error page has been assigned as a bug, and we'll be
looking at it.
David Schnur
Dartware, LLC
http://www.dartware.com
Charley Kline wrote:
Maybe I just missed it, but there does not seem to be a way to have a
custom probe of any sort put the device icon into the newer "Critical"
state. This is important to be able to do when writing probes against
telecom equipment, as they have three kinds of standard alarm
severities, "Critical", "Major", and "Minor", which would map nicely
onto "Critical", "Alarm", and "Warning", except there doesn't seem to
be any way to reach that "Critical" state from a custom probe.
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
