analysis.cfg not working?
list Sean Clark
Have an odd thing that popped up with analysis.cfg I renamed all of my groups in hosts.cfg so that everything was consistent – then tried this in analysis.cfg: DISPLAYGROUP="Bastion" PROC /usr/bin/pt-heartbeat 2 8 red However, this PROC got applied to all hosts in the hosts.cfg (and procs went red for ~800 hosts or so, until I removed it) Is it an issue with analysis.cfg? Or because I use the group bastion several times in hosts.cfg, or? Snippet of hosts.cfg: group Script Servers 0.0.0.0 some.VIP.that.monitored.elseware # NET:tools-mon page Oceanic group Bastion 10.249.5.8 monitor-01.somedomain.com # NET:oceanic-mom group Web Servers 10.249.5.2 web-01.somedomain.com # NET:oceanic-mom page rio-texas RIO Production Servers group VIP 0.0.0.0 anotherVIP.monitored.elseware# NET:xymon-server group Bastion 127.0.0.1 rio-monitor-01.somedomain.com # NET:rio-tex This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
list Jeremy Laidman
▸
On 28 March 2014 00:59, Clark, Sean <user-2db5fbcae9a7@xymon.invalid> wrote:
Is it an issue with analysis.cfg? Or because I use the group bastion several times in hosts.cfg, or?
Could be the multiple listings of the same group. Not sure. Have you tried running "xymond_client --test" and see what that shows?
list Sean Clark
Shows blank: LOG /var/log/mysqld.log MATCH=ERROR COLOR=red HOST=%rio-db-*.* (line: 332) [ that is last stanza before the DISPLAYGROUP= line, which is below] PROC /usr/bin/pt-heartbeat 2 8 red (line: 336) UP 3600 -1 (line: 342) LOAD 1.00 3.00 (line: 343) DISK * 90% 95% 0 -1 red (line: 344) MEMREAL 100 101 (line: 345) So that DISPLAYGROUP="Bastion" line gets lumped in with the default lines So, I can see why it's red/applied to all – it thinks it should be But, I knew that much already, hence my email to the group :-D The man page for analysis.cfg says DISPLAYGROUP='blah' is one of the valid ways of selecting dudes… but then it's missing
▸
From: Jeremy Laidman <user-71895fb2e44c@xymon.invalid<mailto:user-71895fb2e44c@xymon.invalid>>
Date: Sunday, March 30, 2014 at 9:30 PM
To: Sean Clark <user-2db5fbcae9a7@xymon.invalid<mailto:user-2db5fbcae9a7@xymon.invalid>>
Cc: Xymon Email List <xymon at xymon.com<mailto:xymon at xymon.com>>
Subject: Re: [Xymon] analysis.cfg not working?
On 28 March 2014 00:59, Clark, Sean <user-2db5fbcae9a7@xymon.invalid<mailto:user-2db5fbcae9a7@xymon.invalid>> wrote:
Is it an issue with analysis.cfg? Or because I use the group bastion several times in hosts.cfg, or?
Could be the multiple listings of the same group. Not sure.
Have you tried running "xymond_client --test" and see what that shows?
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
list Sean Clark
It just doesn't appear to work at all
I changed it so there were no duplicate groups
Xymon host.cfg:
group fortification
10.24.32.75 unified-monitor-01.somedomain.com # NET:xymon-server
Analysis.cfg:
DISPLAYGROUP="fortification"
PROC /usr/bin/pt-heartbeat 2 8 red
That line gets applied to all hosts as a default, not the single host in the group 'fortification'
Xymond_client —test ?dump shows it applied to all (and the gui did as well)
▸
From: <Clark>, Sean Clark <user-2db5fbcae9a7@xymon.invalid<mailto:user-2db5fbcae9a7@xymon.invalid>>
Date: Monday, March 31, 2014 at 1:30 PM
To: Jeremy Laidman <user-71895fb2e44c@xymon.invalid<mailto:user-71895fb2e44c@xymon.invalid>>
Cc: Xymon Email List <xymon at xymon.com<mailto:xymon at xymon.com>>
Subject: Re: [Xymon] analysis.cfg not working?
Shows blank:
LOG /var/log/mysqld.log MATCH=ERROR COLOR=red HOST=%rio-db-*.* (line: 332)
[ that is last stanza before the DISPLAYGROUP= line, which is below]
PROC /usr/bin/pt-heartbeat 2 8 red (line: 336)
UP 3600 -1 (line: 342)
LOAD 1.00 3.00 (line: 343)
DISK * 90% 95% 0 -1 red (line: 344)
MEMREAL 100 101 (line: 345)
So that DISPLAYGROUP="Bastion" line gets lumped in with the default lines
So, I can see why it's red/applied to all – it thinks it should be
But, I knew that much already, hence my email to the group :-D
The man page for analysis.cfg says DISPLAYGROUP='blah' is one of the valid ways of selecting dudes… but then it's missing
From: Jeremy Laidman <user-71895fb2e44c@xymon.invalid<mailto:user-71895fb2e44c@xymon.invalid>>
Date: Sunday, March 30, 2014 at 9:30 PM
To: Sean Clark <user-2db5fbcae9a7@xymon.invalid<mailto:user-2db5fbcae9a7@xymon.invalid>>
Cc: Xymon Email List <xymon at xymon.com<mailto:xymon at xymon.com>>
Subject: Re: [Xymon] analysis.cfg not working?
On 28 March 2014 00:59, Clark, Sean <user-2db5fbcae9a7@xymon.invalid<mailto:user-2db5fbcae9a7@xymon.invalid>> wrote:
Is it an issue with analysis.cfg? Or because I use the group bastion several times in hosts.cfg, or?
Could be the multiple listings of the same group. Not sure.
Have you tried running "xymond_client --test" and see what that shows?
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.