[Xymon] Pushing client status with bbwincmd.exe

[Nathan Riley]

Hello all, I am working on pushing some data that I have collected and formatted on my clients into my Xymon 4.3.4 installation. Basically, the issue is that I cannot get the alerts to trigger for these specific hosts/services. All my other alerting works great, and I was hoping someone might have some insight. Let me walk you through the process:

- First, on the server, I updated the TEST2RRD variable in xymonserver.cfg to reflect my new columns that the clients will be reporting on (shortened for readability):
 TEST2RRD=cpu=la,disk,inode,..................,vmware,vmware-cpu,vmware-memory,vmware-storage,vmware-datastore,vmware-chassis,vmware-guest"

- Secondly, I updated the hosts.cfg file:

page vmware VMWare Servers
group-except conn|trends <H3><B><font face="Tahoma, Arial, Helvetica">VMWare ESXi Servers</font></B></H3>
0.0.0.0 my-dc09.root.whatever # noconn vmware vmware-chassis vmware-cpu vmware-datastore vmware-memory vmware-storage

0.0.0.0    vmware2.root.something  # noconn vmware vmware-chassis vmware-cpu vmware-datastore vmware-memory vmware-storage

-Third, I updated the alerts.cfg:

PAGE=vmware
        SCRIPT /usr/lib/xymon/server/ext/emailConnector.sh alert at email.com REPEAT=24h SERVICE=vmware,vmware-chassis,vmware-cpu,vmware-datastore,vmware-memory,vmware-storage


Now that the server side is done, I run this command on the client:
   BBWinCmd.exe myserver.com:1984 status my-dc09.root.whatever vmware-cpu red $CPUmessage


Command works good. I see that in Xymon the vmware-memory column for my-dc09.root.whatever went red, and the main vmware page I defined in hosts.cfg is red as well.

Here is where things start to go bad, I cannot get it to alert on this. So I ran an additional troubleshooting command from the server:

me at monitor:/usr/lib/xymon/server$ ./bin/xymoncmd --env=/usr/lib/xymon/server/etc/xymonserver.cfg xymond_alert --test my-dc09.root.whatever vmware-cpu --duration 501

00002392 2013-08-02 10:00:35 send_alert my-dc09.root.whatever:vmware-cpu state Paging
00002392 2013-08-02 10:00:35 Matching host:service:page 'my-dc09.root.whatever:vmware-cpu:vmware' against rule line 123
00002392 2013-08-02 10:00:35 Failed 'HOST=*' (color)
00002392 2013-08-02 10:00:35 Matching host:service:page 'my-dc09.root.whatever:vmware-cpu:vmware' against rule line 141
00002392 2013-08-02 10:00:35 Failed 'PAGE=vmware' (color)
00002392 2013-08-02 10:00:35 Matching host:service:page 'my-dc09.root.whatever:vmware-cpu:vmware' against rule line 148
00002392 2013-08-02 10:00:35 Failed 'PAGE=servers' (pagename not in include list)
00002392 2013-08-02 10:00:35 Matching host:service:page 'my-dc09.root.whatever:vmware-cpu:vmware' against rule line 150
00002392 2013-08-02 10:00:35 Failed 'HOST=%(ns1|silver|red).whatever.com' (hostname not in include list)

The part that is very strange to me is this line: 00002392 2013-08-02 10:00:35 Failed 'PAGE=vmware' (color)

This seems to tell me that it matched on the page vmware as it should, but did not match due to color, even though the vmware page and the my-dc09.root.whatever vmware-cpu column is absolutely red.

I have tried adding in things like COLOR=Red to my hosts.cfg but it still fails in the same way.

Thanks in advance for any help or ideas you may have.

-Nathan Riley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20130802/5eced300/attachment.html>