v3.0November 23, 2016 |
Advanced Monitors Added |
||||||||||||||||||
New |
Several new monitors have been created focused on security and performance. These are:
|
||||||||||||||||||
Changed |
Several monitoring stations have been added across the globe. | ||||||||||||||||||
Fixed |
Contact creation was failing on new accounts.
The default 'Websites' dashboard was not restricting the reports to website monitors. Performance issues were causing some updates to not occur. |
||||||||||||||||||
Planned |
Release of a public API. This will be for account management and reporting.
More communication methods for contacts. |
v2.0August 5, 2016 |
HTTPS monitoring added |
New |
A new HTTPS monitor type is supported. It monitors for HTTPS uptime, performance and functionality.
Certificates can now be setup to specify how many days before expiration to send alerts. This can be used in conjunction with contact escalations (see below) to create a series of alerts as the expiration date approaches. The prior version defaulted to seven days. Peformance reporting on HTTPS. Uptime reporting on HTTPS. You can also set up a test to match expected text on the site to validate the site is operational and not producing error pages or hacked. A status page that combines certificate and HTTPS data. User-definable dashboards. State change reporting. This is when a monitor switches state from up to down or down to up. The ability to turn off monitoring stations. The ability to pause monitors. The ability to run ad-hoc tests from the monitors page. Contact sets and escalations: Contacts now can be set up to send to multiple sets for email and SMS endpoints. This allows you to create named sets of contacts that can be modified without having to modify each monitor. Each contact set can be set to wait a certain amount of time prior to sending notifications. This can be used as an escalation process. Reporting: The log report (and all new reports) now support:
|
Changed |
Contacts are now structured as named sets of endpoints. This significantly departs from the original structure of a simple list of contacts.
When setting up monitors, you now can select multiple contact sets, instead of picking which individual contacts to alert. |
Fixed |
False positives: This is a situation where transient errors on the web would cause alerts to be sent out. To prevent this, a
confirmation test is performed from another station prior to any alerts being sent out.
This issue has created the need for logging both unconfirmed errors and confirmed errors separately. On occasion, certificates were showing a status of 'Unknown', when they were actually expired. |
Planned |
Release of a public API. This will be for account management and reporting.
More monitor types. The ability to select cipher sets for certificates. More communication methods for contacts. |