Services Watch Type
Microsoft Windows services are long-running executable applications runnng in their own Windows sessions. These services can be automatically started when the computer boots, can be paused and restarted, and usually do not show any user interface.� Services can run in the context of a specific user account that is different from the logged-on user, or the default computer account.
How does it work?
WebWatchBot monitors Windows Services on local and non-local Windows systems by:
- Monitoring the state of the Service: running or not running.
- Monitoring CPU usage %.
- Monitoring the memory usage.
- Monitoring the total number of threads.
- Ensure that a critical Service is running.
- Ensure that unwanted Servicees are not running.
- Raise awareness of Services consuming too much CPU time.
- Track memory usage of a Service.
- Monitor fluctuations of Service threads.
Fields and Buttons
Computer Name - name of computer with Windows service to be monitored
Name - Service name to monitor - The name of the service.
Select - Opens the "Select Service" dialog, which displays a list of active processes to choose from:
Running - if unchecked, watch item will fail if the Service is running
CPU Usage % - threshold for triggering an alert
Memory Usage - threshold for triggering an alert
Thread Count - threshold for triggering an alert
Service monitoring on non-local Windows systems requires access to the remote system registry. The remote registry service must be running on the non-local machine.