|
|
|
|
Put WebWatchBot at the Center of Your Server Monitoring Plan
|
WebWatchBot supports more than 20 different monitoring types,
including the ability to custom monitors and watch items.
|
|
The following table reviews the software's monitoring capabilities in a number of key areas:
|
| Transactions |
WebWatchBot monitors the sequence of steps taken by an end user
of the web application, website, and/or intranet, including logging
into an application, selecting an account, viewing data, posting data
to a form, using a shopping cart, and logging out.
|
| Recorder |
The Recorder allows the administrator to easily create a complex
but typical user transaction as a watch item. Using the Recorder,
administrators simply follow the desired sequence of user steps and
save this recording as a watch item to be replayed by WebWatchBot
during the monitoring process.
|
| HTTP/HTTPS |
WebWatchBot verifies that a specified URL is available and responding
within a defined threshold. It can download the content from a
specified URL and verify that specific content strings are found. Web
form monitoring is accomplished by automatically submitting form
data to simulate user actions. In addition, the software provides easy
configuration of dynamic URLs, session ids, and other parameters.
|
| Databases |
WebWatchBot monitors all major databases by connecting,
executing a query, and searching results for specified text.
|
| Servers |
Ensuring that complex web applications and websites are running
properly requires keeping a constant eye on a wide range of servers
and support infrastructure, such as email servers, DNS servers,
and routers. WebWatchBot provides a wealth of monitoring items,
including:
Ping: queries any IP device that allows pinging over TCP/IP
Port: connects to a server via a URL or IP address and specified
port number to verify availability and response time
SMTP (Outgoing Email Servers): monitors outgoing email servers
and user accounts for availability and performance
POP3 (Incoming Email Servers): monitors incoming email servers
and user accounts for availability and performance
FTP: logs in and verifies that a file can be uploaded to, or downloaded
from, an FTP server |
| System |
System level monitors for physical and operating system components
of the infrastructure include:
File: verifies the existence of a specified file and searches for
content within the file
Disk Usage: sets thresholds for disk usage and issues alerts when
usage exceeds thresholds
Performance Counters: monitors Windows performance counters
to capture and analyze data provided by applications, services, and
drivers; helps determine system bottlenecks and problem areas to
better tune system and application performance
Process (Windows): monitors Windows processes to capture and
analyze key statistics, including CPU and memory usage and total
number of threads; helps ensure processes are running as expected
and using acceptable levels of CPU and memory resources
Services (Windows): monitors Windows services to capture and
analyze key statistics, including CPU and memory usage and total
number of threads; helps ensure services are running as expected
and using acceptable levels of CPU and memory resources
Event Log: scans and filters system messages recorded by most
Windows applications, including but not limited to information,
warning, and error messages that can have an impact on the
server and its services and applications; ensures mission-critical
applications are operating normally and eases the task of manually
scanning messages
Custom System Monitors: provides easy extensibility of monitoring
capabilities so that external programs and scripts, such as thirdparty
network analysis tools, can be executed and analyzed
|
|
|
|