Hi Tom,

Excellent, thanks!

I overlooked leaving the entity type at "state".

All good now.


Lane Eckley
Vice President of Operations
Hypernia Corporation

Email: lane@staff.hypernia.com
Desk: 1.305.390.2124
Cell Phone: 1.305.308.0526
Email to SMS: 3125022380@vzwpix.com
 leckley01    laneeckley    www.hypernia.com
 
 
Confidentiality Note: The information contained in this transmission is legally privileged and confidential, intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. Thank you!


On Mon, Aug 18, 2014 at 5:57 AM, Tom Laermans <tom.laermans@powersource.cx> wrote:
Lane,

This should work fine with what you're doing.

device_status is 0
device_status_type is ping

and

device_status is 0
device_status_type is snmp

Make sure to set the checker entity type to device.

Tom

On 08/18/2014 11:33 AM, Lane Eckley wrote:
Hi Guys,

I am attempting to setup an alert checker for when a server goes into a "down" state for either SNMP or Ping - ideally I would like to create one alert checker for each (ping & snmp).

Reviewing the metrics documentation I believe I should be using a combination of the following two:

device_status (0 = down, 1 = up)
device_status_type (reason for down, 'snmp'/'ping')

Using the above I am failing miserably it seems as I am unable to get the alert checker to "match" a machine I turned off to do the testing.

Can anyone share a quick step by step on how to setup this alert checker correctly?

Thanks!

-Lane


_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium


_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium