[Xymon] Xymon Powershell Windows client

Gavin Stone-Tolcher g.stone-tolcher at its.uq.edu.au
Mon Feb 23 02:00:36 CET 2015


Just a comment, the field widths for the display of 1K blocks for the "disk" output should probably be increased from "9" to "10" or "11" to allow for terabyte class devices?

Also the old BB client used to display the volume name enclosed in "()" after the "Mounted" field.

e.g.

Filesystem   1K-blocks     Used    Avail Capacity  Mounted
C             142632960 43665264 98967696    30%    /FIXED/C ()
D             142734336 56339072 86395264    39%    /FIXED/D (DATA)
F             314572800  6421984 308150816     2%    /FIXED/F (AUDIT)
G             314572800 264085248 50487548    83%    /FIXED/G (SHARED)
I             629145600 608879424 20266156    96%    /FIXED/I (PROJECTS1)
J             629145600 234245312 394900288    37%    /FIXED/J (PROJECTS2)
K             629145600 267088320 362057280    42%    /FIXED/K (USERS)

Some of the Windows guys at my site would like to see that info in the powershell client test output.

I wonder if a new field "Label" or "Volume" column could be added between the "Mounted" and "Summary" fields with that information.
The "VolumeName" field from Win32_LogicalDisk class could be used for the data?

I have added it locally and it does not seem to effect RRD collection or graphing for the test.
This is what I currently have being generated using a locally modified version of the client.

Filesystem       1K-blocks       Used      Avail  Capacity                Mounted      Label      Summary(Total\Avail GB)
C                104753148   42324428   62428720       40%               /FIXED/C        (SYSTEM) 99.90\59.54

I am using the "Label" field from Win32_Volume class for the data in this particular case.


Cheers,
Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident Response
Information Technology Services
The University of Queensland
Level 4, Prentice Building, St Lucia 4072
T: +61 7 334 66645, M: +61 401 140 838
E: g.stone-tolcher at its.uq.edu.au<mailto:g.stone-tolcher at its.uq.edu.au> W: www.its.uq.edu.au<http://www.its.uq.edu.au>

ITS: Service. Team. Accountability. Results.

IMPORTANT: This email and any attachments are intended solely for the addressee(s), contain copyright material and are confidential. We do not waive any legal privilege or rights in respect of copyright or confidentiality. Except as intended addressees are otherwise permitted, you do not have permission to use, disclose, reproduce or communicate any part of this email or its attachments. Statements, opinions and information not related to the official business of The University of Queensland are neither given nor endorsed by us. By using this email (including accessing any attachments or links) you agree we are not liable for any loss or damage of any kind arising in connection with any electronic defect, virus or other malicious code we did not intentionally include.

Please consider the environment before printing this email.

CRICOS Code 00025B

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of zak.beck at accenture.com
Sent: Friday, 13 February 2015 7:53 PM
To: xymon-developer at lists.sourceforge.net; xymon at xymon.com
Subject: [Xymon] Xymon Powershell Windows client

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20150223/15c3929e/attachment.html>


More information about the Xymon mailing list