Example Alert Checkers

These alert checkers can be copy and pasted in to your Observium installation or modified to fit your requirements. Details of available metrics and attributes to be used for alert checkers can be found in the Entity Type Reference.

We use device hostname match * as a method to match all entities.

Alert Name Entity Type Boolean / Check Conditions Association Rules
Device down Device ANY device_status equals 0 device hostname match *
Processor is above 80% Processor ANY processor_usage greater 80 device hostname match *
Linux Average CPU above 80% Processor ANY processor_usage greater 80 device os is linux and
processor description match *average*
Linux Swap above 80% Memory ANY mempool_perg ge 80 device os equals linux and
mempool description match *swap*
Memory is above 70% Memory ANY mempool_perc greater 70 device hostname match *
Status is ALERT! Status ANY status_event equals alert device hostname match *
Status is WARN! Status ANY status_event equals warn device hostname match *
Fanspeed is out of threshold Sensor ANY
sensor_value greater @sensor_limit
sensor_value less @sensor_limit_low
sensor class equals fanspeed
Temperature out of threshold Sensor ANY
sensor_value greater @sensor_limit
sensor_value less @sensor_limit_low
sensor class equals temperature
Traffic exceeds 85% Port ANY
ifInOctets_perc ge 85
ifOutOctets_perc ge 85
port ifType equals ethernetCsmacd
BGP Session to AS41552 down BGP Peer ALL
bgpPeerAdminStatus notequals stop
bgpPeerState notequals established
BGP Peer ASN equals 41552
Storage exceeds 85% of disk Storage ANY storage_perc ge 85 storage type equals hrStorageFixedDisk
Port has encountered errors Port ANY
ifInErrors_rate gt 1
ifOutErrors_rate gt 1
port ifType equals ethernetCsmacd
Port is enabled, but operationally down Port ALL
ifAdminStatus equals up
ifOperStatus notequals up
port ifType equals ethernetCsmacd

Further examples can be seen on our Live Demo