windows powershell client 🔗 link

What's the status of the powershell windows client?  I have a few 
windows servers that need to be monitored and thought I'd try the power 
shell client instead of BBWin, if the shell client is ready.

Tom,

What's the status of the powershell windows client?  I have a few 
windows servers that need to be monitored and thought I'd try the 
power shell client instead of BBWin, if the shell client is ready.

The following is still the state of play:
http://lists.xymon.com/oldarchive/2011/01/msg00244.html

On the only Windows host where I need to run external scripts, I am
running XymonPSClient as the client and BBWin with everything else
turned off except externals to run those scripts.

David.

--
David Baldwin - IT Unit
Australian Sports Commission          www.ausport.gov.au
Tel 02 62147830 Fax 02 62141830       PO Box 176 Belconnen ACT 2616
user-cbbf693f2c89@xymon.invalid          Leverrier Street Bruce ACT 2617


Keep up to date with what's happening in Australian sport visit
http://www.ausport.gov.au

This message is intended for the addressee named and may contain
confidential and privileged information. If you are not the intended
recipient please note that any form of distribution, copying or use of
this communication or the information in it is strictly prohibited and
may be unlawful. If you receive this message in error, please delete it
and notify the sender.

Cc: xymon at xymon.com
Subject: Re: [Xymon] windows powershell client

I try this new client, but I get error. I have try IP address and dns
name entry, same result.
Try it on windows 7 x64.

Exception calling "GetHostAddresses" with "1" argument(s): "No such host
is known"
At C:\Xymon\xymonsend.ps1:10 char:65
+         $srvIPs = $srvparams[0] | %{[system.net.dns]::GetHostAddresses
<<<< ($_)} | %{ $_.IPAddressToString}
    + CategoryInfo          : NotSpecified: (:) [],
MethodInvocationException
    + FullyQualifiedErrorId : DotNetMethodException

XymonSend : Cannot connect to host xymonhost () :
System.Management.Automation.MethodInvocationException: Exception cal
ling "Connect" with "2" argument(s): "Value cannot be null.
Parameter name: addresses" ---> System.ArgumentNullException: Value
cannot be null.
Parameter name: addresses
   at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32
port)
   at System.Net.Sockets.TcpClient.Connect(IPAddress[] ipAddresses,
Int32 port)
   at Connect(Object , Object[] )
   at
System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object
target, Object[] arguments, MethodInforma
tion methodInformation, Object[] originalArguments)
   --- End of inner exception stack trace ---
   at
System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object
target, Object[] arguments, MethodInforma
tion methodInformation, Object[] originalArguments)
   at System.Management.Automation.ParserOps.CallMethod(Token token,
Object target, String methodName, Object[] paramAr
ray, Boolean callStatic, Object valueToSet)
   at System.Management.Automation.MethodCallNode.InvokeMethod(Object
target, Object[] arguments, Object value)
   at System.Management.Automation.MethodCallNode.Execute(Array input,
Pipe outputPipe, ExecutionContext context)
   at System.Management.Automation.ParseTreeNode.Execute(Array input,
Pipe outputPipe, ArrayList& resultList, Execution
Context context)
   at
System.Management.Automation.StatementListNode.ExecuteStatement(ParseTre
eNode statement, Array input, Pipe output
Pipe, ArrayList& resultList, ExecutionContext context)
At line:1 char:11
+  xymonsend <<<<  "ping" "xymonhost"
    + CategoryInfo          : OpenError: (:) [Write-Error],
WriteErrorException
    + FullyQualifiedErrorId :
Microsoft.PowerShell.Commands.WriteErrorException,XymonSend

David Raymond-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf
Of David Baldwin
Sent: Thursday, March 31, 2011 0:17
To: Tom Georgoulias
Cc: xymon at xymon.com
Subject: Re: [Xymon] windows powershell client

Tom,

What's the status of the powershell windows client?  I have a few 
windows servers that need to be monitored and thought I'd try the 
power shell client instead of BBWin, if the shell client is ready.

The following is still the state of play:
http://lists.xymon.com/oldarchive/2011/01/msg00244.html

On the only Windows host where I need to run external scripts, I am
running XymonPSClient as the client and BBWin with everything else
turned off except externals to run those scripts.

David.

--
David Baldwin - IT Unit
Australian Sports Commission          www.ausport.gov.au
Tel 02 62147830 Fax 02 62141830       PO Box 176 Belconnen ACT 2616
user-cbbf693f2c89@xymon.invalid          Leverrier Street Bruce ACT 2617


Keep up to date with what's happening in Australian sport visit
http://www.ausport.gov.au

This message is intended for the addressee named and may contain
confidential and privileged information. If you are not the intended
recipient please note that any form of distribution, copying or use of
this communication or the information in it is strictly prohibited and
may be unlawful. If you receive this message in error, please delete it
and notify the sender.

Still get the error in powershell, but xymon receive info anyway.
So, I see we can get xymonconfig.cfg in %temp% folder. This file is
empty. How can I set some feature like bbwin.
I would like to monitor some services and other external scripts like
bbwin does.

Thx.

David Raymond

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf
Of Raymond, David
Sent: Wednesday, April 06, 2011 10:23
Cc: xymon at xymon.com
Subject: Re: [Xymon] windows powershell client

I try this new client, but I get error. I have try IP address and dns
name entry, same result.
Try it on windows 7 x64.

Exception calling "GetHostAddresses" with "1" argument(s): "No such host
is known"
At C:\Xymon\xymonsend.ps1:10 char:65
+         $srvIPs = $srvparams[0] | %{[system.net.dns]::GetHostAddresses
<<<< ($_)} | %{ $_.IPAddressToString}
    + CategoryInfo          : NotSpecified: (:) [],
MethodInvocationException
    + FullyQualifiedErrorId : DotNetMethodException

XymonSend : Cannot connect to host xymonhost () :
System.Management.Automation.MethodInvocationException: Exception cal
ling "Connect" with "2" argument(s): "Value cannot be null.
Parameter name: addresses" ---> System.ArgumentNullException: Value
cannot be null.
Parameter name: addresses
   at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32
port)
   at System.Net.Sockets.TcpClient.Connect(IPAddress[] ipAddresses,
Int32 port)
   at Connect(Object , Object[] )
   at
System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object
target, Object[] arguments, MethodInforma
tion methodInformation, Object[] originalArguments)
   --- End of inner exception stack trace ---
   at
System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object
target, Object[] arguments, MethodInforma
tion methodInformation, Object[] originalArguments)
   at System.Management.Automation.ParserOps.CallMethod(Token token,
Object target, String methodName, Object[] paramAr
ray, Boolean callStatic, Object valueToSet)
   at System.Management.Automation.MethodCallNode.InvokeMethod(Object
target, Object[] arguments, Object value)
   at System.Management.Automation.MethodCallNode.Execute(Array input,
Pipe outputPipe, ExecutionContext context)
   at System.Management.Automation.ParseTreeNode.Execute(Array input,
Pipe outputPipe, ArrayList& resultList, Execution
Context context)
   at
System.Management.Automation.StatementListNode.ExecuteStatement(ParseTre
eNode statement, Array input, Pipe output
Pipe, ArrayList& resultList, ExecutionContext context)
At line:1 char:11
+  xymonsend <<<<  "ping" "xymonhost"
    + CategoryInfo          : OpenError: (:) [Write-Error],
WriteErrorException
    + FullyQualifiedErrorId :
Microsoft.PowerShell.Commands.WriteErrorException,XymonSend

David Raymond-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf
Of David Baldwin
Sent: Thursday, March 31, 2011 0:17
To: Tom Georgoulias
Cc: xymon at xymon.com
Subject: Re: [Xymon] windows powershell client

Tom,

What's the status of the powershell windows client?  I have a few 
windows servers that need to be monitored and thought I'd try the 
power shell client instead of BBWin, if the shell client is ready.

The following is still the state of play:
http://lists.xymon.com/oldarchive/2011/01/msg00244.html

On the only Windows host where I need to run external scripts, I am
running XymonPSClient as the client and BBWin with everything else
turned off except externals to run those scripts.

David.

--
David Baldwin - IT Unit
Australian Sports Commission          www.ausport.gov.au
Tel 02 62147830 Fax 02 62141830       PO Box 176 Belconnen ACT 2616
user-cbbf693f2c89@xymon.invalid          Leverrier Street Bruce ACT 2617


Keep up to date with what's happening in Australian sport visit
http://www.ausport.gov.au

This message is intended for the addressee named and may contain
confidential and privileged information. If you are not the intended
recipient please note that any form of distribution, copying or use of
this communication or the information in it is strictly prohibited and
may be unlawful. If you receive this message in error, please delete it
and notify the sender.

-- 
David Baldwin - IT Unit
Australian Sports Commission          www.ausport.gov.au
Tel 02 62147830 Fax 02 62141830       PO Box 176 Belconnen ACT 2616
user-cbbf693f2c89@xymon.invalid          Leverrier Street Bruce ACT 2617

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Steve Brown
Sent: Thursday, June 01, 2017 3:39 PM
To: 'xymon at xymon.com'
Subject: [Xymon] Windows Powershell client

Hi
We have a Linux server for the xymon server (4.3.18) but we run the bb-central addon so my client-local.cfg on the server is pretty bare. All of our xymon clients are Linux servers until now.
I've recently installed the xymon Windows powershell client. Most of it is working except the columns  files, ports, procs, and svcs. They are reporting a 'clear' status because I haven't defined anything to check.

Where and how do I configure these columns?  From my research it seems I should configure client-local.cfg on the Linux server but I'm unsure how to configure it for access to Windows.  I see there is a [win32] section but it is blank.  The Windows Powershell client is running on a Windows 2012 server.

Would anyone be willing to share how they've configured these columns or some basic examples?
For example if I want to monitor
files matching C:\*.log,
ports 22,8080
procs prowin32 C:\Progressx86\OpenEdge\bin\prowin32.exe
svcs sshd, Spooler

In addition where do I configure the Red, Yellow, Green for these columns ?

Thank you for your help
Steve

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Steve Brown
Sent: 02 June 2017 20:38
To: 'xymon at xymon.com' <xymon at xymon.com>
Subject: [External] [Xymon] Windows powershell client

Hi,

I'm adding a new client into our server.  I added some 'files' to the client-local.cfg on the server. As soon as I did that, the xymonclient.log column went purple.  I tried adding log:C:\xymonclinet.log:10240 into the client-local.cfg but that did not resolve the purple status.
There's no entry in the analysis.cfg for log.  The msgs column reports 'No entries in xymonclient.log '

What do I need to do to get the xymonclient.log column to report correctly and turn green again?
Thank you for your help
Steve

Client-local.cfg snip

[sgb-sandbox-01]
file:C:\data\db\*.lg
log:C:\xymonclient.log:10240


analysis.cfg snip

HOST=sgb-sandbox-01
        UP      1h
        LOAD    5.0 10.0
        DISK    * 90 95
        MEMPHYS 100 101
        MEMSWAP 50 80
        MEMACT  90 97
        PROC "_mprosrv" 1 5 red
        PROC "prowin32.exe" 1 5 red
        FILE "C:\data\db\admdemo.lg" SIZE<2048M TRACK=admdemoLg yellow
        FILE "C:\data\db\mfgdemo.lg" SIZE<2048M TRACK=mfgdemoLg yellow
        FILE "C:\data\db\hlpdemo.lg" SIZE<2048M TRACK=hlpdemoLg yellow

From: Beck, Zak [mailto:user-aada0fa38bf8@xymon.invalid]
Sent: Monday, June 05, 2017 11:04 AM
To: Steve Brown <user-a23886790dfc@xymon.invalid>; 'xymon at xymon.com' <xymon at xymon.com>
Subject: RE: [External] [Xymon] Windows powershell client

Hi Steve

Could you attach the xymonclient.log from the client server? Remove any IPs or confidential info if needed.

Thanks

Zak

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Steve Brown
Sent: 02 June 2017 20:38
To: 'xymon at xymon.com' <xymon at xymon.com<mailto:xymon at xymon.com>>
Subject: [External] [Xymon] Windows powershell client

Hi,

I'm adding a new client into our server.  I added some 'files' to the client-local.cfg on the server. As soon as I did that, the xymonclient.log column went purple.  I tried adding log:C:\xymonclinet.log:10240 into the client-local.cfg but that did not resolve the purple status.
There's no entry in the analysis.cfg for log.  The msgs column reports 'No entries in xymonclient.log '

What do I need to do to get the xymonclient.log column to report correctly and turn green again?
Thank you for your help
Steve

Client-local.cfg snip

[sgb-sandbox-01]
file:C:\data\db\*.lg
log:C:\xymonclient.log:10240


analysis.cfg snip

HOST=sgb-sandbox-01
        UP      1h
        LOAD    5.0 10.0
        DISK    * 90 95
        MEMPHYS 100 101
        MEMSWAP 50 80
        MEMACT  90 97
        PROC "_mprosrv" 1 5 red
        PROC "prowin32.exe" 1 5 red
        FILE "C:\data\db\admdemo.lg" SIZE<2048M TRACK=admdemoLg yellow
        FILE "C:\data\db\mfgdemo.lg" SIZE<2048M TRACK=mfgdemoLg yellow
        FILE "C:\data\db\hlpdemo.lg" SIZE<2048M TRACK=hlpdemoLg yellow


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.

I'm having one hell of a time tracking this down.  Where is the Powershell client?  I want to add the link to Xymonton.  Is this the correct url?

https://sourceforge.net/p/xymon/code/HEAD/tree/sandbox/WinPSClient/

Zak

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Galen Johnson
Sent: 22 June 2017 02:42
To: xymon at xymon.com
Subject: [External] [Xymon] Windows Powershell client

Hey,

I'm having one hell of a time tracking this down.  Where is the Powershell client?  I want to add the link to Xymonton.  Is this the correct url?

Or is there a better place to get it?

thanks

=G=


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.

www.accenture.com

                DISK    * 90 95
                MEMPHYS 100 101
                MEMSWAP 50 80
                MEMACT  90 97

Zak

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of KC Kuhns
Sent: 09 November 2017 15:11
To: xymon at xymon.com
Subject: [External] [Xymon] Windows PowerShell Client

I'm trying to configure alerts to be managed locally on the Windows PowerShell clients instead of controlling them from the Xymon server. I want to have the clients manage their own thresholds in this situation.

I have my xymonclient_config.xml set to use local settings and reference a localclient.cfg file that has all the values in it. Even with it setup this way, it isn't reporting on the correct thresholds. I can have my CPU at 101 and still receive alerts when it hits 6%. Am I missing something since the localclient.cfg comes defined with Linux values? I.e. 6.5 9.5 instead of 65% 95%? I know it's designed to managed all from Xymon but I'd like the option to manage locally on some machines.


Xymonclient_config.xml

<?xml version="1.0"?>
-<XymonSettings>
<servers>xymon.example.com</servers>
<clientlogfile>c:\Xymon\xymonclient.log</clientlogfile>
<clientconfigfile>c:\xymon\localclient.cfg</clientconfigfile>
<clientname>Server.Name</clientname>
<clientfqdn>0</clientfqdn>
<clientlower>0</clientlower>
<clientremotecfgexec>0</clientremotecfgexec>
</XymonSettings>


Localclient.cfg

DEFAULT
                # These are the built-in defaults.
                UP      30
                LOAD    95.0 100.0
                DISK    * 90 95
                MEMPHYS 100 101
                MEMSWAP 50 80
                MEMACT  90 97


Thanks for the help!


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.

www.accenture.com

Subject: Re: [Xymon] Windows PowerShell Client

Hi


You cannot manage alerts locally from the Powershell client, it is simply not supported.


Sorry!


Zak


From: Xymon [mailto:xymon-bounces at xymon.com]
On Behalf Of KC Kuhns

Sent: 09 November 2017 15:11

To: xymon at xymon.com

Subject: [External] [Xymon] Windows PowerShell Client


I’m trying to configure alerts to be managed locally on the Windows PowerShell clients instead of controlling them from the Xymon server. I want to have the clients manage their own thresholds in this situation.


I have my xymonclient_config.xml set to use local settings and reference a localclient.cfg file that has all the values in it. Even with it setup this way, it isn’t reporting on the correct thresholds. I can have my CPU
at 101 and still receive alerts when it hits 6%. Am I missing something since the localclient.cfg comes defined with Linux values? I.e. 6.5 9.5 instead of 65% 95%? I know it’s designed to managed all from Xymon but I’d like the option to manage locally on
some machines.


Xymonclient_config.xml


<?xml version="1.0"?>

-<XymonSettings>

<servers>xymon.example.com</servers>

<clientlogfile>c:\Xymon\xymonclient.log</clientlogfile>

<clientconfigfile>c:\xymon\localclient.cfg</clientconfigfile>

<clientname>Server.Name</clientname>

<clientfqdn>0</clientfqdn>

<clientlower>0</clientlower>

<clientremotecfgexec>0</clientremotecfgexec>


</XymonSettings>


Localclient.cfg


DEFAULT

# These are the built-in defaults.

UP 30

LOAD 95.0 100.0


DISK * 90 95

MEMPHYS 100 101

MEMSWAP 50 80


MEMACT 90 97


Thanks for the help!


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.


www.accenture.com

On Fri, 10 Nov 2017, John Tullis wrote:

I think the goal is to configure thresholds from the client like we do with bbwin, not necessarily the alerts.

If it's not currently an option, is anyone working on making it possible?