bbwin test results not showing up in xymon
list DavidB
I've been debugging an issue and have had no success in resolving it. I'm using a custom test with BBWin 0.12 installed on Windows 2008 R2 server. My test leaves it's results in the designated tmp directory and BBWin picks up the results and deletes them from the folder but the results never get to the xymon server. The results do not show up as a column for the host nor do I get a ghost report. I find nothing in the server logs or the client logs to give my any help. The server is xymon 4.2.0 but I've also tried it against a xymon 4.2.3 instance that I have running. The usual client side tests (cpu, disk, etc) are reporting as expected so that indicates that the client is talking to the server. These tests are currently working properly on a Windows 2003 server (that is about to be taken out of service) with an older xymon client. Here's my bbwin configuration file: <?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="timer" value="300" /> <setting name="bbdisplay" value="xymonserve.mydomain.com:1984" /> <!-- BB Pager Part --> <setting name="usepager" value="true" /> <setting name="bbpager" value="xymonserve.mydomain.com:1984" /> <setting name="pagerlevels" value="red purple" /> <!-- proxy connection settings --> <!-- <setting name="useproxy" value="false" /> <setting name="proxy" value="[user:password@]host[:port]" /> --> <!-- bbwin mode local or central --> <setting name="mode" value="local" /> <setting name="configclass" value="win32" /> <setting name="autoreload" value="true" /> <setting name="timer" value="1m" /> <load name="cpu" value="cpu.dll" /> <load name="disk" value="disk.dll" /> <load name="externals" value="externals.dll"/> <load name="filesystem" value="filesystem.dll"/> <load name="memory" value="memory.dll"/> <load name="msgs" value="msgs.dll"/> <load name="procs" value="procs.dll" /> <load name="stats" value="stats.dll"/> <load name="svcs" value="svcs.dll" /> <load name="uptime" value="uptime.dll"/> <load name="who" value="who.dll"/> <setting name="loglevel" value="4" /> <setting name="logpath" value="C:\Progra~2\BBWin\logs\BBWin.log" /> <!-- If true, the agent will report reporting failures as warning events --> <setting name="logreportfailure" value="true" /> </bbwin> <cpu> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="default" warnlevel="80%" paniclevel="95%" /> </cpu> <disk> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- Level can be given by % or size unit mb, gb, tb --> <setting name="default" warnlevel="90%" paniclevel="95%" /> <setting name="E" warnlevel="90%" paniclevel="95%" /> <setting name="C" warnlevel="90%" paniclevel="95%" /> <!-- custom rules examples <setting name="C" warnlevel="70%" paniclevel="400mb" /> <setting name="M" ignore="true" /> --> <!-- If true, the agent will check remote drives --> <setting name="remote" value="false" /> <!-- If true, the agent will check that cd/dvdrom drives are empty --> <setting name="cdrom" value="false" /> </disk> <externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <load value="C:\Progra~2\PillarWatch\PillarMSGS.exe" timer="2m" /> <load value="C:\Progra~2\PillarWatch\PillarTSK.exe" timer="2m" /> <load value="C:\Progra~2\PillarWatch\PillarNFS.exe" timer="2m" /> <load value="C:\Progra~2\PillarWatch\PillarSAN.exe" timer="2m" /> <load value="C:\Progra~2\PillarWatch\PillarHDWR.exe" timer="2m" /> </externals> <memory> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="physical" warnlevel="95%" paniclevel="98%" /> <setting name="page" warnlevel="80%" paniclevel="90%" /> </memory> <msgs> <setting name="delay" value="30m" /> <match logfile="sys" type="err" alarmcolor="green" /> <match logfile="sys" type="warn" alarmcolor="green" /> <match logfile="app" type="err" alarmcolor="green" /> <match logfile="app" type="warn" alarmcolor="green" /> <!-- Ignore rules --> </msgs> <procs> <!-- some procs rules example <setting name="drwtsn" rule="-1" alarmcolor="red" /> <setting name="pageant.exe" rule="=1" comment="Putty agent deamon" /> --> </procs> <svcs> <setting name="alwaysgreen" value="false" /> <setting name="alarmcolor" value="yellow" /> <setting name="autoreset" value="false" /> <setting name="Microsoft Forefront Client Security State Assessment Service" value="=started" autoreset="false" alarmcolor="red" /> <!-- <setting name="SQL Server (MSSQLSERVER)" value="=started" autoreset="false" alarmcolor="red" /> --> <setting name="Big Brother Hobbit Client" value="=started" autoreset="false" alarmcolor="red" /> </svcs> <uptime> <setting name="delay" value="60m" /> <setting name="alarmcolor" value="yellow" /> </uptime> </configuration> here's what my registry entries look like: binpath REG_SZ C:\ProgramFiles(x86)\BBWin\bin etcpath REG_SZ C:\Program Files(x86)\BBWin\etc hostname REG_SZ server1.mydomain.com tmppath REG_SZ C:\Program Files(x86)\BBWin\ext Note: I changed the tmppath from the default "tmp" - the test results are written to the ext directory Here's a sample output of a test: server50.mydomain.com:green Wed 20 9:45:22 2011 [server50.mydomain.com] <center><br>No current messages.</center> Note: The test is being run on server1 but it is testing some functionality on server50 (which is an appliance that can't run xymon client) and reporting it as server50. If anyone can shed any light on this issue I would appreciate it. David B
list Malcolm Hunter
Hi David,
▸
----- Original Message ----- From: DavidB Sent: 07/21/11 03:02 PM To: xymon at xymon.com Subject: [Xymon] bbwin test results not showing up in xymon I've been debugging an issue and have had no success in resolving it. I'm using a custom test with BBWin 0.12 installed on Windows 2008 R2 server. My test leaves it's results in the designated tmp directory and BBWin picks up the results and deletes them from the folder but the results never get to the xymon server. The results do not show up as a column for the host nor do I get a ghost report. I find nothing in the server logs or the client logs to give my any help. The server is xymon 4.2.0 but I've also tried it against a xymon 4.2.3 instance that I have running. The usual client side tests (cpu, disk, etc) are reporting as expected so that indicates that the client is talking to the server. These tests are currently working properly on a Windows 2003 server (that is about to be taken out of service) with an older xymon client.
Here's a sample output of a test: server50.mydomain.com:green Wed 20 9:45:22 2011 [server50.mydomain.com] <center><br>No current messages.</center> Note: The test is being run on server1 but it is testing some functionality on server50 (which is an appliance that can't run xymon client) and reporting it as server50. If anyone can shed any light on this issue I would appreciate it.
The format of your test needs to be like this: green 20/07/2011 9:45:22 [server50.mydomain.com] <center><br>No current messages.</center> HTH Malcolm
list DavidB
Thank you very much for your reply! You're suggestion worked and I can now see the results of the custom tests in hobbit. Now I have an additional hurdle. I need the report to be for a host name other than the name of the host that the test is being sent from. Is that possible with the externals functionality of bbwin? ----- Forwarded Message ----- From: Malcolm Hunter <user-8c18ec239c05@xymon.invalid> To: xymon at xymon.com Cc: Sent: Thursday, July 21, 2011 5:43 PM Subject: Re: [Xymon] bbwin test results not showing up in xymon
▸
Hi David,
----- Original Message ----- From: DavidB Sent: 07/21/11 03:02 PM To: xymon at xymon.com Subject: [Xymon] bbwin test results not showing up in xymon I've been debugging an issue and have had no success in resolving it. I'm using a custom test with BBWin 0.12 installed on Windows 2008 R2 server. My test leaves it's results in the designated tmp directory and BBWin picks up the results and deletes them from the folder but the results never get to the xymon server. The results do not show up as a column for the host nor do I get a ghost report. I find nothing in the server logs or the client logs to give my any help. The server is xymon 4.2.0 but I've also tried it against a xymon 4.2.3 instance that I have running. The usual client side tests (cpu, disk, etc) are reporting as expected so that indicates that the client is talking to the server. These tests are currently working properly on a Windows 2003 server (that is about to be taken out of service) with an older xymon client.
Here's a sample output of a test: server50.mydomain.com:green Wed 20 9:45:22 2011 [server50.mydomain.com] <center><br>No current messages.</center> Note: The test is being run on server1 but it is testing some functionality on server50 (which is an appliance that can't run xymon client) and reporting it as server50. If anyone can shed any light on this issue I would appreciate it.
The format of your test needs to be like this: green 20/07/2011 9:45:22 [server50.mydomain.com] <center><br>No current messages.</center> HTH Malcolm
list Richard Finegold
Such is possible with the bbwincmd.exe included. First, create the file somewhere with the first line having a format with FQDN periods replaced by commas: status <host>.<column> color <text> status server50,mydomain,com.pmsgs green Wed 20 9:45:22 2011 [server50.mydomain.com] No current messages. Some of the <text> may be later exploited by supplemental reports or custom notification scripts, and text below the first line may be parsed for RRDs, but generally it's freeform, although the convention is to put the date and server name and a microsummary in the first line. Personally, I don't know why you'd use a <br> before a short microsummary, or <center> tags when the text is already centered on the web page, and the tag doesn't seem handy in a message subject, but perhaps there's a use case that I haven't envisioned or has slipped my mind. I will admit to using <br> tags _within_ a long microsummary that lended itself to more lines, e.g. my http://communities.quest.com/docs/DOC-5579 script: "OK <BR> Good as of Tuesday, August 31, 2010 9:16:32 AM (booted)<BR> Last abend Wednesday, February 10, 2010 6:28:01pm (201 days earlier)" More details via "man bb", look for "status". After that file is created (e.g. "server50.pmsgs"), use bbwincmd uploadmessage. Confirm it supports "uploadmessage" by running it at the command line (the documentation at runtime may be more current than the .chm, 0.12 supports it). bbwincmd.exe xymonserve.mydomain.com:1984 uploadmessage path\to\server50.pmsgs
▸
On Mon, Jul 25, 2011 at 08:44, DavidB <user-0b035f809adc@xymon.invalid> wrote:Now I have an additional hurdle. I need the report to be for a host name other than the name of the host that the test is being sent from. Is that possible with the externals functionality of bbwin? ----- Forwarded Message ----- From: Malcolm Hunter <user-8c18ec239c05@xymon.invalid>----- Original Message ----- From: DavidB Sent: 07/21/11 03:02 PM To: xymon at xymon.com Subject: [Xymon] bbwin test results not showing up in xymon I've been debugging an issue and have had no success in resolving it. I'm using a custom test with BBWin 0.12 installed on Windows 2008 R2 server. My test leaves it's results in the designated tmp directory and BBWin picks up the results and deletes them from the folder but the results never get to the xymon server. The results do not show up as a column for the host nor do I get a ghost report. I find nothing in the server logs or the client logs to give my any help. The server is xymon 4.2.0 but I've also tried it against a xymon 4.2.3 instance that I have running. The usual client side tests (cpu, disk, etc) are reporting as expected so that indicates that the client is talking to the server. These tests are currently working properly on a Windows 2003 server (that is about to be taken out of service) with an older xymon client.Here's a sample output of a test: server50.mydomain.com:green Wed 20 9:45:22 2011 [server50.mydomain.com] <center><br>No current messages.</center> Note: The test is being run on server1 but it is testing some functionality on server50 (which is an appliance that can't run xymon client) and reporting it as server50. If anyone can shed any light on this issue I would appreciate it.The format of your test needs to be like this: green 20/07/2011 9:45:22 [server50.mydomain.com] <center><br>No current messages.</center>
list DavidB
Thanks for the reply! A little experimentation at the command line indicates that this probably a workable solution. I thought of this approach but wasn't sure it would work because sometimes the test results could be voluminous and it could overwhelm the command line. I didn't know about uploadmessage option and didn't see it in the documentation for bbwin.
▸
----- Original Message ----- From: Richard Finegold <user-6a016aac278a@xymon.invalid> To: DavidB <user-0b035f809adc@xymon.invalid> Cc: "xymon at xymon.com" <xymon at xymon.com> Sent: Wednesday, July 27, 2011 3:53 AM Subject: Re: [Xymon] Fw: bbwin test results not showing up in xymon Such is possible with the bbwincmd.exe included. First, create the file somewhere with the first line having a format with FQDN periods replaced by commas: status <host>.<column> color <text> status server50,mydomain,com.pmsgs green Wed 20 9:45:22 2011 [server50.mydomain.com] No current messages. Some of the <text> may be later exploited by supplemental reports or custom notification scripts, and text below the first line may be parsed for RRDs, but generally it's freeform, although the convention is to put the date and server name and a microsummary in the first line. Personally, I don't know why you'd use a <br> before a short microsummary, or <center> tags when the text is already centered on the web page, and the tag doesn't seem handy in a message subject, but perhaps there's a use case that I haven't envisioned or has slipped my mind. I will admit to using <br> tags _within_ a long microsummary that lended itself to more lines, e.g. my http://communities.quest.com/docs/DOC-5579 script: "OK <BR> Good as of Tuesday, August 31, 2010 9:16:32 AM (booted)<BR> Last abend Wednesday, February 10, 2010 6:28:01pm (201 days earlier)" More details via "man bb", look for "status". After that file is created (e.g. "server50.pmsgs"), use bbwincmd uploadmessage. Confirm it supports "uploadmessage" by running it at the command line (the documentation at runtime may be more current than the .chm, 0.12 supports it). bbwincmd.exe xymonserve.mydomain.com:1984 uploadmessage path\to\server50.pmsgs On Mon, Jul 25, 2011 at 08:44, DavidB <user-0b035f809adc@xymon.invalid> wrote:
Now I have an additional hurdle. I need the report to be for a host name other than the name of the host that the test is being sent from. Is that possible with the externals functionality of bbwin? ----- Forwarded Message ----- From: Malcolm Hunter <user-8c18ec239c05@xymon.invalid>----- Original Message ----- From: DavidB Sent: 07/21/11 03:02 PM To: xymon at xymon.com Subject: [Xymon] bbwin test results not showing up in xymon I've been debugging an issue and have had no success in resolving it. I'm using a custom test with BBWin 0.12 installed on Windows 2008 R2 server. My test leaves it's results in the designated tmp directory and BBWin picks up the results and deletes them from the folder but the results never get to the xymon server. The results do not show up as a column for the host nor do I get a ghost report. I find nothing in the server logs or the client logs to give my any help. The server is xymon 4.2.0 but I've also tried it against a xymon 4.2.3 instance that I have running. The usual client side tests (cpu, disk, etc) are reporting as expected so that indicates that the client is talking to the server. These tests are currently working properly on a Windows 2003 server (that is about to be taken out of service) with an older xymon client.Here's a sample output of a test: server50.mydomain.com:green Wed 20 9:45:22 2011 [server50.mydomain.com] <center><br>No current messages.</center> Note: The test is being run on server1 but it is testing some functionality on server50 (which is an appliance that can't run xymon client) and reporting it as server50. If anyone can shed any light on this issue I would appreciate it.The format of your test needs to be like this: green 20/07/2011 9:45:22 [server50.mydomain.com] <center><br>No current messages.</center>
list Malcolm Hunter
▸
----- Original Message ----- From: DavidB Sent: 07/27/11 05:13 PM To: xymon at xymon.com Subject: Re: [Xymon] Fw: bbwin test results not showing up in xymon Thanks for the reply! A little experimentation at the command line indicates that this probably a workable solution. I thought of this approach but wasn't sure it would work because sometimes the test results could be voluminous and it could overwhelm the command line. I didn't know about uploadmessage option and didn't see it in the documentation for bbwin.
I'm currently working on the manual. I'll try to document all of the new features for the next release. I'm finding new things to do all the time and it's difficult to stay focussed on one thing. Malcolm
list Scot Kreienkamp
Can you give us any idea how close to release right now? Thanks, Scot Kreienkamp
▸
-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Malcolm Hunter
Sent: Wednesday, July 27, 2011 5:44 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Fw: bbwin test results not showing up in xymon
----- Original Message ----- From: DavidB Sent: 07/27/11 05:13 PM To: xymon at xymon.com Subject: Re: [Xymon] Fw: bbwin test results not showing up in xymon Thanks for the reply! A little experimentation at the command line indicates that this probably a workable solution. I thought of this approach but wasn't sure it would work because sometimes the test results could be voluminous and it could overwhelm the command line. I didn't know about uploadmessage option and didn't see it in the documentation for bbwin.
I'm currently working on the manual. I'll try to document all of the new features for the next release. I'm finding new things to do all the time and it's difficult to stay focussed on one thing. Malcolm
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
list Malcolm Hunter
▸
----- Original Message ----- From: Scot Kreienkamp Sent: 07/28/11 02:01 AM To: Malcolm Hunter, xymon at xymon.com Subject: RE: [Xymon] Fw: bbwin test results not showing up in xymon Can you give us any idea how close to release right now?
We're still deciding on that. There's a fair amount of work to do, but I'm hoping within the next month. Regards, Malcolm
list Henrik Størner
Here's a sample output of a test:
server50.mydomain.com:green Wed 20 9:45:22 2011 [server50.mydomain.com]<center><br>No current messages.</center>
Note: The test is being run on server1 but it is testing some functionality on server50 (which is an appliance that can't run xymon client) and reporting it as server50.Are you sure about the "<servername>:color" syntax in the output file ? I haven't seen that before - I assumed BBWin would always report the status-messages as belonging to the host that BBWin runs on (picking up the status-name from the name of the outputfile). If I am right, then Xymon sees a status with an unrecognizable color-name, and therefore the message is discarded. Regards, Henrik