[Xymon] Xymon PS Client - v2.34

[Timothy Williams]

Zak, I've been testing the new v2.34 PS client before elevating into
production environment. I've found that the ServiceCheck function skips out
without checking any service status, unless there is a discrete
'noservicecheck' entry in the clientconfig.cfg file. Having only
'servicecheck:' entries are inoperative. I have fixed it on my copy by
encapsulating the subroutine for noservicecheck (about lines  2466 to 2522)
in another if statement.

 if ($serviceexclds -ne "") { .. for each.. } ending just before the
writelog ("Checking service..)

*Timothy L. Williams*

Operating Systems Analyst
Virginia Commonwealth University Computer Center



On Wed, Dec 12, 2018 at 11:55 AM Ribeiro, Glauber via Xymon <xymon at xymon.com>
wrote:

>
>
>
> ---------- Forwarded message ----------
> From: "Ribeiro, Glauber" <glauber.ribeiro at experian.com>
> To: "Beck, Zak" <zak.beck at accenture.com>, "xymon at xymon.com" <
> xymon at xymon.com>
> Cc:
> Bcc:
> Date: Wed, 12 Dec 2018 15:31:28 +0000
> Subject: RE: Xymon PS Client - v2.34
>
> Excellent, thank you!
>
>
>
> Please remind me, where can I download the client, and how would one
> upgrade (is it enough to replace the PowerShell scripts with the new
> versions?).
>
>
>
> g
>
>
>
> *From:* Xymon [mailto:xymon-bounces at xymon.com] *On Behalf Of *Beck, Zak
> *Sent:* Wednesday, December 12, 2018 09:05
> *To:* xymon at xymon.com
> *Subject:* [Xymon] Xymon PS Client - v2.34
>
>
>
> Hi
>
>
>
> A long-overdue release with a number of minor fixes and one major overhaul
> of event log processing.
>
>
>
> Event log processing changes:
>
>
>
> You’ve always been able to exclude certain event log messages from
> appearing using ‘ignore’ – this actually had a major issue where a matching
> ignore filter suppressed other events. I have added the opposite: being
> able to include only the messages you’re interested in. That means you now
> have two ways of handling which event log messages you see:
>
>
>
>    - Exclude mode: including all events except specified – use ignore
>    - Include mode: ignore all events except specified – use include
>
>
>
> Include mode takes priority - if there are any “include” entries, include
> mode will be used. All ignore entries will be disregarded.
>
>
>
> Secondly, to cover the scenario where you are using client local config
> merging, you can now specify a priority on eventlogswanted which will allow
> you to override other configs. For example, you may have an eventlogswanted
> statement in your [powershell] class with some sensible defaults, like this:
>
>
>
> eventlogswanted:System:1000:Warning,Critical,Error
>
>
>
> But if you have a specific server where you also want to check the
> Application log, you can override that statement in a [server] block with
> this:
>
>
>
> eventlogswanted:100:Application,System:1000:Warning,Critical,Error
>
>
>
>
>
>
>
> List of all the fixes:
>
>
>
> * added TLS fix from Kris Springer / Jonathan Trott. Only set TLS
> parameters if https is used for downloads (of updates and external
> scripts). Note that these TLS settings are not compatible with Powershell
> v2 (but will only impact if you use https)
>
> * optionally only show listening ports in [ports], controlled from
> client-local.cfg (using ports:listenonly)
>
> * allow disabling of IIS sites information, controlled from
> xymonclient_config.xml
>
> * added 'noservicecheck' from Tim Williams
>
> * extra logging in XymonMsgs
>
> * fixed major bug in XymonMsgs where a matching 'ignore' filter would
> suppress all events
>
> * fix for unnecessary attempt to encrypt serverHttpPassword
>
> * event log handling overhaul
>
> * allow different levels by event log
>
> * handling of multiple configs when using config merging (priority on
> eventlogswanted)
>
> * add ability to use environment variables for clientname if network
> settings not available
>
>
>
> Zak
>
>
>
>
> ------------------------------
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy. Your privacy is important to us.
> Accenture uses your personal data only in compliance with data protection
> laws. For further information on how Accenture processes your personal
> data, please see our privacy statement at
> https://www.accenture.com/us-en/privacy-policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
>
>
>
> ---------- Forwarded message ----------
> From: "Ribeiro, Glauber via Xymon" <xymon at xymon.com>
> To: "Beck, Zak" <zak.beck at accenture.com>, "xymon at xymon.com" <
> xymon at xymon.com>
> Cc:
> Bcc:
> Date: Wed, 12 Dec 2018 15:31:28 +0000
> Subject: Re: [Xymon] Xymon PS Client - v2.34
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20190104/f890da8c/attachment.html>