You can configure receiving automatic alerts to get notified whenever your monitor(s) report a problem.

To receive alerts, you need first to create contacts in your Monitis account. You can create contacts of different types, to be alerted by one of the following methods:

• Email – We allow sending unlimited number of email alerts.
Note: Your email contacts will be used also for sending you weekly and daily SLA and performance reports (see Reports).
• SMS (Short Message Service) – You will be receiving alerts via SMS as soon as you have positive SMS notifications balance (see SMS Balance/SMS Buy).
• Phone Call – You can receive a call at the number of your choice anytime, day or night.
• Phone Call & SMS – You will be alerted via both phone call and SMS.

• IM – You will be receiving alerts via instant messaging service. Currently, we support Google Talk.
• Twitter – You will be receiving alerts via Twitter notifications.
• URL callback – You will be receiving alerts via URL callbacks.
• Push Notifications – Install Monitis mobile application on your iOS or Android device to receive alerts on the go.
• PagerDuty – Integrate with PagerDuty to receive PagerDuty alerts according your set up escalation policy.

See Adding Contacts and Managing Contacts for detailed instructions on how to create contacts of different types.

Events that result in alerting are defined by your monitor’s configuration and the assigned Alert Rule(s).

Depending on the monitor type and configuration, you can receive alerts when e.g. your server fails to respond within predefined timeout, your website returns an HTTP error (see HTTP Error Codes), your web page or some page element fails to load, your set threshold for a metric (e.g. CPU, RAM) is crossed by your machine, content matching fails for your website, some system event occurs, etc.

See Adding Alert Rules and Managing Alert Rules for detailed instructions on how to set up alerting for your monitors.

Alert Rules define conditions that if violated trigger sending alerts. Depending on monitor type, e.g. for Uptime, Transaction and Full Page Load monitors Alert Rules can be based on number of repetitive failures per location and the number of locations for the monitor to fail from. For server-device monitors just number of repetitive failures is alerted upon, as our monitoring agent runs locally on your machine. For some monitors, Alert Rules can specify also status changes in the monitored system, or occurrence of some system events that will result in sending alerts (see Configuring Alert Rules for Different Monitor Types).

When your monitor fails you will receive a problem alert. When setting up the Alert Rule, you can also choose to be alerted continuously if the problem persists (see Number of Problem Alerts Sent).

Information provided in the problem alert depends on the monitor type. Typically, problem alert will provide you with information about the failed monitor (name, group, URL, etc), problem date/time, locations that the external monitor has failed from, problem description, etc.

A sample problem alert (for Uptime Monitor, email format) is shown below.

Service: HTTP
Group Name: Default
Date/Time: 2-27-2014 12:09:10 (GMT + 4)
Additional Information: Failed to receive HTTP response. IP Resource temporarily unavailable
Failures From: US-MID, US-WST

And when your monitor recovers from failure, you will receive a recovery alert.

A sample recovery alert (for Uptime Monitor, email format) is shown below:

Service: HTTP
Group Name: Default
Date/Time: 2-27-2014 12:10:09 (GMT + 4)
Additional Information: HTTP response code: 200, IP
Downtime: 49 second(s)

Information provided in the recovery alert depends on the monitor type. Typically, in addition to monitor data it will show you the result of the last monitoring check run and the downtime, calculated as time difference between the first problem alert and the recovery alert (see Downtime Calculation in Alerts and Alerts History).