What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Request for new sensor process & wmi

Votes:

0

I have a couple of windows services running which I can monitor in 2 ways.

1. using the wmi service sensor 2. using the wmi process sensor

The problem is that I want to functionality of both!

The service sensor allows me to restart the service automatically from prtg without extra sensors or batch files but it only monitors the channel 'running (msec)' which is not really helpful.

the wmi process sensor gives me working set, commit size, cpu info (per instance), threads, handles, cpu info (total) and the total number of instances running but has no built in way to restart a proces if it somehow has stopped working. :(

Is there some way to combine the resetting of the service with the extra information?

process prtg9 restart service wmi

Created on Oct 18, 2011 2:00:49 PM



3 Replies

Votes:

0

Dear Thomas,

I'm afraid this can only be done using two sensors in the moment, since they base on different WMI Classes.

best regards.

Created on Oct 18, 2011 4:08:03 PM by Torsten Lindner [Paessler Support]



Votes:

0

Hi Thomas,

You can setup a trigger that starts a batch notification when the wmi process sensor goes down. In this batch file you can restart the service.

As of Windows XP, you can use sc.exe to stop and start a service on a remote computer

sc \\server stop service
sc \\server start service

Regards,

Created on Oct 18, 2011 5:06:54 PM



Votes:

0

Hi Gerard,

Thank you for your suggestion. My main concern was trying to do it without extra batch scripts. The problem is that in my experience the WMI sensors can go to a down state even when they are in fact not down but there is an intermittent problem with WMI.

So instead of restarting the service on a down state, I'd rather like to do it based on a value like memory usage as these have proven to be more reliable an indicator of that the WMI sensor beeing down.

Oh well, I'll start my powershell editor again :)

Created on Oct 19, 2011 8:57:35 AM




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.