Hi all,
Since 4.2.0 Hobbit officially supports the GROUP-label mechanism for distinguishing processes, disks, files, etc. When I quote Henrik correctly "alerts in both BB and Hobbit trigger on a status column.", this gives me the following problem.
Let's say we have the following config:
hobbit-clients.cfg:
SERVER=name DISK / 90 95 GROUP=unix DISK /database 90 95 GROUP=dba
hobbit-alerts.cfg:
GROUP=dba MAIL dba at somewhere.com bla bla
GROUP=unix MAIL unix at somewhere.com bla bla
The threshold for /database is exceeded, status is yellow, mail is sent to the dba. Great! Now the /-partition starts to grow, the status remains yellow because the dba's are investigating the problem but have not solved the issue, but the unix-team is not alerted because no status change has occured.
Any hints???
Below I found a discussion from last year, when I think the idea was born and the term LABEL was introduced but is called GROUP now.
Thanks, Peter
2005/11/13, Scott Walters <scott at packetpushers.com>:
On Fri, 11 Nov 2005, (Henrik Stoerner) wrote:
the rules you define in the hobbit-clients.cfg file. E.g. if you have two process checks for a host, the check for the "httpd" process can be associated with a "web" label, and the check for the "mysqld" process gets a "database" label. Then you can define alerts that use these labels just like we currently use e.g. the service names, i.e.
HOST=* MAIL dbadmin at foo.com LABEL=database MAIL webadmin at foo.com LABEL=web
Beautiful. And it would be ideal if those 'labels' also ended up as columns in the display, not just for notifications.
So for the the 'database' label, you would like to see mysql up, nothing bad in the log file, and the /mysql partition is OK.
-- Scott Walters -PacketPusher