Hi
I'm not sure I understand the question fully, I'm sure there will be other people on the list who can help.
The client runs as a Windows service and monitors the space and processes running on that one server. It then reports back those results every 5 minutes (by default) to the Xymon server.
If you're asking whether this client can be running on server 1 and monitor server 2, no, it cannot. As far as I know, Xymon is not really designed like that.
However, if each node is attached to shared storage, and the storage is presented as a mapped drive, then yes, it can monitor that. You'd need to use in the local config:
<wanteddisks>3 4</wanteddisks>
and use the update I committed earlier today.
Thanks
Zak
From: Dito [mailto:user-b8c0e0047c63@xymon.invalid]
Sent: 17 February 2015 13:53
To: Beck, Zak; user-834d44be5e50@xymon.invalid; xymon at xymon.com
Subject: Re: [Xymon] Xymon Powershell Windows client
can it be used in a MS cluster resource? can I monitor sql resource and space on it, independently of which node it is running on?
On Fri, Feb 13, 2015, 06:35 null <user-aada0fa38bf8@xymon.invalid <mailto:user-aada0fa38bf8@xymon.invalid> > wrote:
Hi all,
Today I have uploaded a new version of the Xymon Powershell client to SVN (in sandbox/WinPSClient). We (Accenture) are very pleased to be contributing these changes to the open source community. I've been working on this now for around 8 months on and off and hopefully the changes made will be of benefit to everyone!
Whilst making changes, we have focussed mainly on making it work, improving reliability and most importantly improving performance.
In most cases, on our 64 bit OS virtual machines, a data collection now takes around 5 seconds. On heavily loaded (CPU load or event log load) servers, the script is now considerably faster than originally. Key to this has been reducing the amount of WMI usage as this was a major culprit.
We have also implemented some new features, largely based on our in-house requirements but hopefully useful to others:
* Showing the process owner and command line in [procs]. This has been implemented using c# code, compiled at runtime.
* Adding Active Directory replication test, Terminal Services sessions test
* Ability to restart any stopped Windows service
* Client self-update
* Dirsize and dirtime checks (which were originally external scripts)
Some things have changed slightly; for example, the local configuration which was registry-based is now XML-based (you can still use registry settings if you prefer). In the SVN repository I have also uploaded a Word document which describes how to install and the configuration options.
I have uploaded all the revisions we have made to SVN so there is a history of development. Whilst we will endeavour to continue contributing changes and improvements in coming months, this is an open source project and as such we are not offering any formal support. If anyone wishes to bugfix, branch or whatever, please do so!
Zak Beck
Accenture