Monthly Archives: December 2011

With the release of monitor-specific alert contacts, the API is updated accordingly and also gained some new methods.

Updates

  • alertContactIDs should be sent when creating or editing monitors to define which alert contacts to be notified of up/down events
  • getMonitors method can now return the alert contacts of a monitor with adding showMonitorAlertContacts=1 to the querystring

New Methods

There are 3 new methods and the names define their functionality well:

  • getAlertContacts
  • newAlertContact
  • deleteAlertContact

The API documentation is updated with all the new information

Once a monitor is detected as down (and back up), Uptime Robot was sending notifications to all alert contacts defined in the “My Settings” page.. until today.

We have rolled an exciting update today where you can assign different alert contacts for each monitor.

Let’s say:

  • you have 10 monitors, 3 of them are your own websites and others belong to customers. And, you want Uptime Robot to notify your customers for “only” the up/down events of their websites,
  • you want to notify the web developer when your company website goes down and notify the IT admin when e-mails server don’t work.

These are all possible now.

How to use it?

Alert contacts are still defined to your account from the “My Settings” page. After that, they can be selected per monitor from the “add and edit monitor” dialogs.

What about my current alert contact settings?

We have assigned your alert contacts to your monitors accordingly. So, everything will keep working how they were.

If you prefer to change the alert contacts of a monitor, simply click the “edit” icon besides it and you’ll see how easy it is.

Did these updates change effect the API?

Yes. There are now new methods and features reflecting the changes. Another blog post is coming about it within a few hours.