Windows Server Monitoring
The Windows monitoring solution consists of 6 probes that
can be run stand-alone or when run simultaneously ensure maximum visibility
into Windows performance and availability.
CPU, Disk & Memory Probe
The CDM Probe monitors key system components such as CPUs,
Disks, and Memory, and detects critical bottlenecks before they have an impact
on system performance. The CDM Probe automatically pre-scans the Windows systems
and defines individual monitoring points and threshold values.
Fig. 1 The CDM Probe allows you to quickly and easily define
performance thresholds and conditions across all your system components.
Fig2. You can also quickly set the timing for data sampling
from each of the various system components to be monitored, and enable system
performance elements to be used for monitoring quality of service against service
level agreements.
Fig3. You can easily define how messages should be displayed
and alerts generated when thresholds are exceeded.
| Features:
- Performance:
- Threshold monitoring with low and high level watermarks
- Graphical presentation of actual and average performance usage as
well as threshold values
- To avoid false positive alarms, i.e. spikes, the interval and sample
rate can easily be configured
- CPU:
- CPU usage (%) - Maximum allowable CPU usage for any process
- Number of processes in the processor queue
- Disk:
- Absolute disk usage (MBs)
- Information retrieval on:
- Local and networked disks
- Total disk space
- Free disk space
- Used (%) disk space
- Memory:
- Pagefile usage (%)
- Swapping/paging activity (pages/s)
|
Windows NT Eventlog Probe
The Windows NT Eventlog Probe automatically scans the NT/2000
Eventlog for essential information in the system, application and security logfiles,
based on predefined monitoring criteria, eliminating the need for time-consuming
and error-prone manual intervention. Sophisticated search facilities speed the
criteria definition process and significantly reduce implementation time.
Fig. 1 The easy configuration of the Windows NT Eventlog Probe.
Fig2. You can easily view status information from the NT Eventlog
| Features:
- System, application and security monitoring
- Simple and powerful watcher definitions
- Regular expressions
- Pattern matching
- Optimized scanning utilities
- Use of intelligent scanning mechanisms to quickly discover and monitor
new entries in the eventlog with minimum overhead
- Polling and event monitoring options
|
Windows Services Probe
The Windows Services Probe detects any service that is not
running according to its profile or that has stopped unexpectedly. It can trigger
predefined automated restart or recovery actions before system performance is
affected or outages occur.The Windows Services Probe collects information on
system, application and network services and issues instant alerts when intervention
is required.
Fig. 1 The easy configuration of the Windows Services Probe.
Fig2. You can easily view status of services
| Features:
- System, application and network service monitoring
- Easy profile definition
- Services to be monitored
- Expected state:
- running or stopped
- Easy-to-define automated recovery and restart actions
- Automatic detection of new services
- Monitoring of restart attempts
|
Processes Probe
The Processes Probe collects information on system, application
and network processes, and monitors windows belonging to a Windows application.
As soon as a process starts to fail or stops unexpectedly, the Processes Probe
issues immediate alerts or launches pre-defined automated recovery and restart
procedures.
Fig. 1 The Processes Probe allows you to quickly and easily
set up monitoring profiles for all your Windows processes.
| Features:
- System, application and network service monitoring
- Easy profile definition
- Services to be monitored
- Expected state:
- running or stopped
- Easy-to-define automated recovery and restart actions
- Automatic detection of new services
- Monitoring of restart attempts
|
Windows Printer Probe
The Windows Printer Probe monitors all local and networked
printers to achieve continuous availability. A printer that is not running according
to its monitoring profile will be discovered at an early stage so that prompt
corrective action can be taken before printing services are disrupted. The Windows
Printer Probe collects information on printers and print jobs and issues instant
alerts when intervention is required.
Fig. 1 Setup of the Windows Printer Probe.
| Features:
- Monitoring of local and networked printers
- Printer status monitoring
- Monitoring the status of elements in the print queue: out of/low on
paper, out of/low on toner, paper jam
- Record-oriented files: complex logfiles with unstructured layout
and multi-line messages
- Print job status monitoring - Pause/error/deletin
|
Logfile Probe
The Logfile Probe scans ASCII-based logfiles and extracts
pre-defined information automatically, eliminating the need for time-consuming
and inherently error-prone manual intervention. Sophisticated built-in utilities
allow the monitoring of very complex logfiles across your systems.
Fig. 1 You can configure the Logfile Probe to monitor your
ASCII-based logfiles based on any number of watcher definitions.
| Features:
- Monitoring of ASCII-based files
- Support for both:
- Line-oriented files:
- standard logfiles with a single line for each message in the file
- Record-oriented files:
- complex logfiles with unstructured layout and multi-line messages
- Simple and powerful watcher definitions by use of:
- Regular expressions
- Pattern matching
- Column positioning
- Character positioning
- Monitoring of multiple logfiles
- Multiple watcher definitions (per logfile)
- Optimized scanning facilities:
- You can scan the whole file or just new entries
|
|
