Yearly Archives: 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.

Since the launch of the API ~a month ago, we are so excited to see many users integrating Uptime Robot ratios to their websites or auto-creating/deleting monitors from their apps.

Also, several wrappers and code samples are shared which eases consuming the "easy-to-use" API more.

As you know, the standard Uptime Robot apiKey can pull and push data for every monitor in an account. You can create create monitors, edit or delete them. But, what if you need to use the API that pulls data from your account but displays it inside a client's website? Revealing the apiKey would be a security issue.

Monitor-specific apiKeys

A new type of apiKey comes to the rescue: monitor-specific apiKeys are now added to the system which enables pulling data of "only" a given monitor.

Each monitor can have their own apiKey and they are locked to use the getMonitors API method only for that monitor.

That is specially functional for web agencies and freelancers controlling multiple clients websites from their own Uptime Robot accounts.

Improvements

The getMonitors method now returns:

Tighter integration for web apps

If you have a web application/service and looking for a tighter integration with Uptime Robot (like creating users via API), please feel free to contact us at [email protected] for more details.

That's all for now : ).

The websites or web pages preferring to stay private and having a password (Basic access authentication), normally returns HTTP 401 status which ends up being marked as “down” by Uptime Robot.

Uptime Robot now has support for monitoring password-protected websites by optionally mentioning the username-password in the monitor’s settings.

The feature exists for both HTTP and Keyword monitors and can be found in the “optional settings” link of “Add New and Edit Monitor dialogs”.

P.S. The API requests, responses and documentation are updated accordingly.

Besides being the developers of Uptime Robot, as website owners, we know that getting notified of downtimes instantly is so important.

Uptime Robot already has a wide range of notification methods: e-mail, text message, Twitter DMs, RSS and API.

Today, we are introducing a new notification method: push notifications for ─░OS -iPhone, iPad And iPod- through the popular and free iOS notification application Boxcar.

Usage is pretty simple:

Also, Boxcar has a Mac Desktop application which can also display the same notifications in your computer.

Does this mean Uptime Robot won’t have an iOS app?

No, it doesn’t. An iOS app for Uptime Robot is planned however we are currently focused on several other “most requested” features like reporting, website widgets and response time analysis.

Once, such core features are ready, we would love to launch a full-featured iOS app. But thought getting push notifications right now would be awesome.

After many requests from the users who would like to integrate Uptime Robot with their apps or create other interfaces for it (like a desktop or mobile), the Uptime Robot API is launched today which makes such integrations possible and so easy.

This is the v1 of the API which covers most of the important stuff including:

  • getting the list of monitors, their details (uptime ratio, URL, friendly name, type, etc.)
  • getting the notification logs for each monitor
  • getting the alert contacts notified after each notification
  • adding new monitors
  • editing monitors
  • deleting monitors.

It is a REST API that can return:

  • XML
  • JSON
  • JSON-p

responses.

In order to use it, simply get your apiKey from the My Settings page and head to the API documentation.

What’s next with the API?

In the next version, we’ll be adding:

  • monitor-specific apiKeys” so you can securely use the apiKey in a client’s website without revealing your main apiKey
  • methods for managing alert contacts (adding/editing/deleting them)

Please share your thoughts about the API and/or any other methods that you think should exist in the next version.

A small update on a fix:a PHP-version update on the server of Uptime Robot’s engine (1.5 days ago) had caused our Twitter DM notifications library to not function properly.

The good news : it is fixed now and working as expected.

Sorry for that guys -and, we have experienced that a serious number of things have changed on PHP 5.3 : )-.

You’ll remember that Uptime Robot is controlling the monitors from multiple locations to double-check and make sure that they are really down or up.

Although things work close to perfect, there are 2 downsides:

  • all the monitoring nodes are located in US datacenters which makes it possible to get false/positives if the “website being monitored” is not hosted in US and there is a communication problem between country/continent-wide networks (it sometimes happens).
  • Uptime Robot’s remote monitors run on shared accounts which can not check port monitors that require full system ownership.

In order to perfect the system, we started running 2 new remote monitoring servers: in Europe (Ireland) and Asia (Singapore) that are placed in Amazon’s Cloud.

So, with the new setup, every monitor will be controlled from 3 continents (North America, Europe and Asia) before it will be marked as down (including port monitors).

These new remote monitoring locations will be activated by 1 August 2011 to make sure that you whitelist the new IPs below if needed / a firewall is used (if you didn’t whitelist any IPs until now and things work ok, there is probably no need to take any actions):

  • 46.137.190.132
  • 122.248.234.23

P.S. And, we’ll be using these new nodes to check and report multi-continent response-times soon :).

Happy monitoring everyone!

This is a very small feature and wanted to activate it before rolling the bigger update that is being working on.

When a monitor goes “down” first and “up” afterwards, Uptime Robot used to send the info: “The monitor XY (http://www.xy.com/) is back up”.

Right now, it includes the amount of downtime so you won’t have to compare the date-times of the notifications for finding the value. It is now like: “The monitor XY (http://www.xy.com/) is back up (it was down since 1 days, 2 hours, 07 minutes and 57 seconds)“.

Hope you like it : ).

Here comes a “frequently requested feature”: Monitoring Ports.

Uptime Robot now enables you to monitor any port/service (like HTTP, FTP, DNS, SMTP, POP, IMAP, etc.) and find out if they are responding or not.

Under the re-organized “Add New Monitor” menu, the feature can be reached by simply selecting “TCP Ports”.

After that, Uptime Robot will be displaying a list of pre-defined/popular ports and the ability to define a custom port.

 

There are usually 2 status options while monitoring a service, it can be:

  • up
  • or down

However, there is a 3rd option from Uptime Robot‘s point of view: it can also be filtered/firewalled. Simply, it can be up or down but the status can not be detected as any requests (like Uptime Robot does) are blocked.

Good news is; if the port/service is behind a firewall and blocks any requests, inside the “down” e-mail notification, you’ll see that Uptime Robot mentions this information.

So, if you have the chance of whitelisting IPs that can reach to the port. If you prefer to, whitelisting Uptime Robot‘s IPs would help the monitor to work (IPs can be found in the “About” page.).

Hope you like this new feature and, now, we can focus on some more tasty stuff : )