Monitoring Capabilities

The core function of Overseer is to monitor your critical IT resources for a problem. Overseer can monitor many different types of resources, and more will be added as time goes on. Overseer will check your resources regularly, based on your configured frequency/schedule, and notify you via Email or txt message if something is wrong.

Overseer Resources Types:

Overseer can monitor devices via ICMP ping. This is the most basic network function test, and is very useful for determining if a computer or network device is available on the network.
Read More about Ping Monitoring
Overseer can monitor websites, hosted via both HTTP and HTTPS/SSL. Web site monitoring is a primary component of most IT monitoring strategies, particularly with more and more software being hosted via websites.
Read More about Website Monitoring
Overseer can monitor Windows event logs, both on local and remote computers. Servers and workstations can be monitored and event log entries can be easily filtered-- so you only see the important stuff. Overseer 5.0 also supports the new Windows 2008 R2 extended event log types('Applications and Services Logs').
Read More about Event Log Monitoring
Overseer can monitor Windows services, both on local and remote computers. Many critical software applications rely on a few core Windows services, so any comprehensive monitoring strategy will have at least a few Windows services being monitored.
Read More about Windows Service Monitoring
Overseer can monitor disk space on any Windows-based computer-- both local and remote. A server that runs out of disk space will likely not be running very long-- so monitoring disk space is critical for the uptime of your networked computer system.
Read More about Windows Disk Space Monitoring
Overseer can monitor Windows processes, running on local or remote computers. Some applications don't run as services, but must be running. It's also possible to inverse the check, and make sure certain applications are NOT running. You can also check to make sure that a specific number of processes of one name are running, that it's not using too much memory or CPU, etc.
Read More about Process Monitoring
Overseer can monitor almost any database using the DB Query resource type. This resource type lets you monitor database connectivity, and even issue a query against the database-- either MSSQL or ODBC. You can evaluate the query results and query execution time to validate the health of your database server, or the content of current data.
Read More about Database Query Monitoring
Overseer can monitor your FTP Servers using the FTP resource type. This resource type lets you monitor FTP Servers to ensure they're responding to login requests, and that those login credentials are working.
Read More about FTP Monitoring
Even if Overseer does not support your specific protocol, it can monitor any service that listens on a TCP Port. The TCP Socket resource type will check to make sure connections are being accepted by a specific host on a specific port, and optionally check to make sure the return text is appropriate for the protocol in question. This can be useful for monitoring SMTP, SSH, POP3, and more.
Read More about TCP Monitoring

Other Monitoring Features:

Agentless Monitoring
Monitors all your resources without installing agents on every computer to be monitored. This saves you significant hours deploying agents to all your computers and upgrading them with new versions.
Monitoring Frequency down to every second
Overseer supports polling resources as quickly as once every second.
Define 1 or more monitoring schedules once, and apply it to as many resources as you'd like. You can edit your schedule and all resources linked to it will automatically change how frequently they monitor, notify, etc.
Monitoring Exceptions
Overseer can be configured to not monitor during defined time frames, such as maintenance periods. This can be done easily on a recurring basis, or one-time basis. All exceptions can be easily viewed in calendar format.
Disable Monitoring
Easily disable any resource-- those that don't need monitoring temporarily, due to maintenance, recovery, or other.