FWIW, I have a number of cases where I have hosts on multiple (sub)pages. I don't use them for the analysis.cfg as much as for the alerts.cfg, but in this way, I can have a page for team x's servers, team y's servers, prod, non-prod, or all server.
--
Mike Burger
AIX Administrator
<http://freedomhome.fhmc.local/intranet/main.jsp>
Phone (317) 537-3680, Fax (317) 537-4680, Cell (317) 797-2040
E-mail: Mike.Burger at FreedomMortgage.com <mailto:Anthony.House at freedommortgage.com>
"Once word leaks out that a pirate's gone soft, people begin to disobey you and then it's nothing but work, work, work, all the time." --Westley/The Dread Pirate Roberts
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Thomas Hawkins Sent: Friday, December 21, 2012 8:22 AM To: xymon at xymon.com Subject: [Xymon] Custom Server Rules for analysis.cfg
We have 50 or 60 servers configured across a number of pages in our xymon instance. Instead of having 60 host=hostname entries with generic entries across all of the servers, I want to set up some groups/tags/etc... that can be applied to a host.
So, I figured out I could do:
PAGE=DELTS/*/*
#Defaults for all DELTS Servers
PROC crond 1 -1 red "TEXT=crond : Task Scheduler"
PROC ntpd 1 -1 yellow "TEXT=ntpd : Network Time Client"To go across all of our servers on our subpages to apply these two proc checks.
What I would like to do is get a bit more specific. We have a mix of physical machines, virtual machines, and linux machines, windows machines, and production machines and development machines.
I'd like to be able to tag hosts somehow so I can do something like this:
Host 1 = Linux, Production, VM
Host 2 = Linux, Physical, Dev
Linux:
PROC - ntp, cron
Production:
PROC - backup client
VM:
PROC - vmwaretools
Physical:
nothing additional.
Dev:
nothing additional
So for Host1 it will do the following PROC tests:
ntp, cron, backup client, vmwaretools
Whereas Host2 will only do:
ntp, cron
I understand that if I had hosts configured into like groups, or subpages then I could target the whole works that way, but I currently have my hosts configured in a way that this is not practical. Essentially I have all hosts divided into 3 major groups, and then a number of subgroups, and then the hosts are listed here based on application cluster or function. Basing it on groups or pages would also require me to create a bunch of additional rules to account for each of the situations above, whereas something like a tag that a host could have multiple of would simplify things.
Can anyone provide any insight as to how I can achieve these goals?
Thanks,
Thomas
CONFIDENTIALITY NOTICE: This e-mail message, including all attachments, is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure, alteration or distribution is strictly prohibited and may violate state or federal law. If you are not the intended recipient, please contact the sender by reply e-mail, delete this email and destroy all copies of the message.