The goal of Monitor Scout is to provide a comprehensive monitoring infrastructure that covers as many monitoring use cases as possible. To this end we supply a number of different monitoring techniques along with a global monitoring network.
Monitor Scouts active monitors allow you to monitor a large number of external services. This includes monitoring of many standardised services like websites (HTTP), FTP, custom TCP ports and more.
Each active monitor lets you select the type of service you wish to monitor from a large selection of pre-defined monitors.
Many monitor types also take take additional parameters for improved user customization.
Active monitors let you select precisely which locations to use to perform the monitoring. The free Monitor Scout package includes 5 monitoring locations while the premium package includes 25 locations.
Select monitoring locations.
And view monitoring data for each selected location.
A number of different graphs are provided for active monitors.
Response time graphs are used to display response times for the monitor, both averages and from each monitoring location.
Uptime graphs can be displayed to visualize uptime for different monitors.
Monitor Scouts passive monitors are used to monitor services that can't be monitored by regular active monitors, either because they are unavailable from the Monitor Scout monitoring network or because there is no monitoring type that can be used to monitor the service.
Passive monitors receive monitoring data (reports) from external services using the Monitor Scout webservice API. This means that a script/program can be created that performs whatever monitoring actions are necessary, and then reports the result to a passive monitor.
Timeouts can be set so that an alert if generated if no report is received within a certain time interval. This means that you will be notified if the script/program feeding the passive monitor stops working.
Passive monitors come in a number of different flavors, boolean monitors tracking a up/down state, and a number of different numerical monitors which can trigger alerts on threshold over/under-runs.
Sending reports to a passive monitor using the Monitor Scout API is done with a simple HTTP request.
Component monitoring in Monitor Scout is used to monitor system components like CPU, memory, load - and also application metrics from for example apache (web server), MySQL etc.
Component monitoring can be enabled in two ways.
HLReporter CPU monitoring gives data for a number of different usage classes.
HLReporter also collects and graphs data for applications like the Apache webserver.
Monitor Scout allows alerts to be sent as either email or sms messages. Alert sending is configurable per user, providing both per user recipient addresses and alert schedules.
Monitor Scout includes an advanced alert manager which provides features such as: