Re: [xymon] bb-win & client-local.cfg

[Vernon Everett <everett.vernon (at) gmail.com>]

On Mon, Jul 26, 2010 at 1:20 PM, Josh Luthman
<josh (at) imaginenetworksllc.com>wrote:

*> Not sure how this would work on Windows.

*I think this statement perfectly encapsulates the problem. :-)

Any Wintendo/bb-win boffins out there?

Cheers
     Vernon




Have you tried LOG?
>
> LOG filename match-pattern [COLOR=color] [IGNORE=ignore-pattern]
> [TEXT=displaytext]
>
> xymon.com example
> LOG /var/log/mail.log DB_RUNRECOVERY COLOR=red
>
> Not sure how this would work on Windows.  Is there any way to identify what
> file is being sent without a packet capture?
>
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
>
> On Mon, Jul 26, 2010 at 12:56 AM, Lapuz, Ryan Jay <
> ryanjay.lapuz (at) tsdp.toshiba.co.jp> wrote:
>
>> Good day!
>>
>>
>>
>> I am also trying to make that work for weeks now. I already read a lot of
>> messages in the xymon archive and bbwin forum but still can’t make it work.
>>
>> The log says “[msgs]: will ignore :  <entry>” but it still sends the
>> ignored data in the client-local.cfg file.
>>
>> Is there someone here who has a working ignore function in the bbwin
>> central mode?
>>
>>
>>
>> Here’s my xymon version.
>>
>> Xymon 4.3.0 beta 2/bbwin 0.12 on CentOS 5-4
>>
>>
>>
>> Thank in advance!
>>
>> Ryan
>>
>>
>>
>> *From:* Vernon Everett [mailto:everett.vernon (at) gmail.com]
>> *Sent:* Monday, July 26, 2010 12:42 PM
>> *To:* xymon (at) xymon.com
>> *Subject:* [xymon] bb-win & client-local.cfg
>>
>>
>>
>> Hi all
>>
>> Hoping for a little help on this one.
>> Got a stream of errors coming through from some wintendo clients running
>> bb-win.
>> See example below.
>> We would like to ignore some errors related to certain messages.
>> I was under the impression that the following in client-local.cfg would do
>> it.
>>
>> [win32]
>> eventlog:Security
>> ignore Success
>> eventlog:System
>> ignore Information
>> *eventlog:Application
>> ignore Citrix System Monitoring
>> ignore MetaFrameEvents*
>>
>> Appears to not be the case.
>> How do we configure the client-local.cfg to ignore instances of the first
>> and last error, but not instances like the middle one below?
>> (The messages are for illustrative purposes only - their relative
>> importance and why I should or shouldn't ignore them is not under
>> discussion)
>>
>> Regards
>>      Vernon
>>
>> [image: red] application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
>>
>>
>>  "The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown
>>  and restart."
>>
>> [image: yellow] application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
>>
>>
>>  "The client does not support HDX MediaStream for Flash. Server-side Flash rendering
>>  will be used if available."
>>
>> [image: yellow] application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
>>
>>
>>  "An error occurred while retrieving client printer properties. Default printer properties
>>  will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName
>>  Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver:
>>
>>  ()"
>>
>>
>