There are two ways for clients to do their job. The default and best (IMO)
way is to have the server do all of the decisions and parsing through logs.
This preferred method is centralized mode. Check to see what yours is
doing. I believe bbwin puts this in the registry.
With centralized mode you make changes on the server. The client simply
sends the information, the raw data, and the server decides green/yellow
red.
With the other mode (maybe client mode?) you make the changes on the client
and the client will then send a green/yellow/red.
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
On Mon, Jul 26, 2010 at 12:42 AM, Vernon Everett
<user-b3f8dacb72c8@xymon.invalid>wrote:
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:
()"