Say I was mixing the commands and had this in client-local.cfg and it applied to both bbwin and powershell clients I might end up with something like:
eventlogswanted:*:250000:warning,critical,error
clientversion:1.98:\\testserver01\test
eventlog:security:10240
ignore “insert some noisy informational event you are ignoring for bbwin but isn’t relevant for PowerShell as it’s not retrieving informational events”
It looks confusing, the eventlog:log_name:max_size command would work for both clients just the powershell client won’t read the size. And Just in general it’s hard to tell which client is doing what. Maybe a solution is to have all the powershell commands start with something unique to the client so the commands can never overlap with bbwin.
Regards,
Brandon
From: David Baldwin [mailto:david.baldwin at ausport.gov.au] Sent: Thursday, 5 March 2015 10:46 AM To: Brandon Dale; zak.beck at accenture.com; jlaidman at rebel-it.com.au Cc: xymon at xymon.com Subject: Re: [Xymon] Xymon PowerShell Windows client
On 5/03/15 10:07 AM, Brandon Dale wrote: The problem is if you are running both bbwin and the powershell client you need a way to be able to setup separate commands in the client-local.cfg for each type of client. If BBWin will just ignore (or at least be unaffected by) the ones it doesn't understand then that shouldn't be a problem, it's only if there are mutual incompatibilities that should be an issue.
David.
Regards,
Brandon