[Xymon] Fw: bbwin test results not showing up in xymon

[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 <goldfndr at gmail.com>
To: DavidB <utadavidb at yahoo.com>
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 <utadavidb at yahoo.com> 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 <malcolm.hunter at gmx.com>
>> ----- 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>