There is never “too much” when it comes to the ways of getting notified about an emergency. And, in some cases, this emergency can be a website or server going down.
Today, voice call notification is added to Uptime Robot and it can be very helpful when we want to make sure that a notification is heard :).
How to add voice call alert contacts?
They are added just like other alert contacts with the steps:
- My Settings>Alert Contacts>New>Voice Call
- Once the number is added, an automated call will reach instantly to deliver an activation code.
- Click the lock icon besides this newly created alert contact and enter the activation code received in the automated call.
- And, attach this alert contact to the monitors of your choice from the add/edit monitor dialogs.
No one prefers to get disturbed and there are ways to make sure the voice calls are received only when there is an important downtime.
Uptime Robot has an advanced notifications feature (in the Pro Plan) to get notified only when the downtime is longer than x minutes and using this feature together with the voice calls will be a smart choice.
Additionally, it may only be the “voice calls for the down notifications” that we prefer to get. A very recently introduced feature also enables that too.
The feature is priced just the same as SMS messages (and a call is considered successful only when the call is answered).
P.S.> As a reminder, it is now possible to get 2x SMS or voice calls for the same price (more details).
Uptime Robot sends notifications for down and up notifications by default for each alert contact type.
However, there can be cases where you may only need the down or up notifications like:
- minimizing the SMS use
- handling only the up or down events via web-hooks
- getting only the SSL expiry notifications but ignoring up/down events
There is now an option inside the new/edit alert contact dialog where we can choose to disable down or up notifications for a given alert contact.
Simple..but it can be powerful :).
This entry was posted on by Umut Muhaddisoglu.
Uptime Robot supports multiple methods to get notified about downtimes on mobile (SMS, push notifications via the mobile app, Pushbullet, Pushover or Boxcar).
And, SMS is one of the most reliable notification methods specially when no data plan exists.
Also, many users prefer to configure their SMS alert contacts as:
- “alert if down for x minutes” (where x is usually 10+) (check this feature)
to make sure that they are notified of longer/important downtimes in case there is no data connectivity.
And, the users can now add 2x more SMS messages for the same price and here are the updated prices:
- 100 SMS – $15
- 200 SMS – $25
- 500 SMS – $55
- 1000 SMS – $100
Also, the SMS messages included in each Pro Plan is doubled as well.
We’ll also be introducing few new features (very soon) to make sure you can use the SMS messages more effectively. Yay!
Getting the notifications inside the team communication app you use can make things easy as this may be where you’ll be discussing how to make that website/server back online.
Besides the Slack integration, Uptime Robot now has support for Microsoft Teams too.
It simply works by creating an incoming webhook URL at the Teams app and creating a new alert contact at Uptime Robot (My Settings>Alert Contacts>New) using this webhook URL.
After that, just attach this alert contact to the monitors of your choice and the notifications will be delivered to the preferred team.
In case you haven’t seen or used it, there is a “Bulk Actions link” just under the “Add Monitor button” in the left sidebar.
It simply opens the “Bulk Actions dialog” and presents a set of actions that can be applied to monitors in bulk.
This feature is now more powerful with few important additions including:
- support for maintenance windows
- support for SSL settings
- applying the actions only to selected monitors (besides all monitors)
- choosing to overwrite or apply by preserving the previous settings
Hope that they will help and we are already working on the expected addition.. which is “bulk importing monitors” :).
Thanks to its bot framework and API support, it is now possible to get down/up/SSL notifications via Telegram messaging app.
The usage is pretty simple:
- go to My Settings>Alert Contacts>New>Telegram
- create the alert contact
- click the unique Telegram link created
- press /start button displayed in the Telegram dialog
- and, you are all set, just attach this alert contact to the monitors of your choice via add/edit monitor dialogs.
Hope that this new feature helps for better notifications.
HTTPs is becoming the “default” for any website whether it is a blog, portal, e-commerce or corporate one.
However, a website with an SSL certificate requires an extra layer of monitoring, “making sure the SSL works as expected”, as a certificate:
- can expire
- can produce errors (host mismatch, use insecure protocols like SSLv3..).
Introducing SSL monitoring
The Pro Plan now monitors such cases and lets you know:
- when the SSL certificate has errors including:
- host mis-match
- forcing insecure protocol (like SSLv2 or SSLv3)
- and when the SSL certificate is getting close to expiry date (when 30, 15, 7 and 1 day is left) so that you can renew it in advance.
Note: “mixed-content SSL warnings and revoked certificates” are currently not supported.
The feature is available by default for all HTTP and keyword monitors whose URLs start with “https”.
Customizing its usage
It is possible to:
- disable SSL monitoring and/or “ignore SSL errors” for selected monitors from the “Add/Edit Monitor dialogs”. This is handy if the website uses a self-signed certificate.
- choose which alert contacts will get “SSL expiry notifications” from the “My Settings>Alert Contacts>Add/Edit Alert Contact dialogs”.
- By default, all alert contact types except “SMS, mobile Push, Pushbullet, Boxcar and Pushover” are enabled considering they are non-intrusive.
Important info: The feature will become active by 20 September 2017 to make sure any customization can be performed in advance.
Excited to have this feature being available and hope that it helps for a better uptime :).
Update (24 Oct 2017)
Thanks to all the feedback received, we have applied a set of updates to make sure that this feature is easy-to-use and functional for everyone:
- a certificate being self-signed is no more a reason for it to be detected as “down”
- monitors with IP-based URLs (like https://220.127.116.11) are not checked for SSL errors
- expiration notifications for certificates by Let’s Encrypt and Cloudflare are only triggered if 3 days or less are left for expiry as these certificates are mostly auto-renewed close to the expiry date.
- ssl settings for all monitors can be changed in bulk using the bulk actions dialog (can be found just under the “Add Monitor button”).
Cloudflare is an impressive service/platform for securing and speeding-up websites.
If you use Cloudflare and have a “status page with a custom-domain” in Uptime Robot, “there may be a small configuration needed” to make sure things work smooth.
Who needs the custom configuration?
If the 3 items below match your case, then the custom config is needed:
- Use Cloudflare as your domain’s DNS provider
- Have a status page with custom domain in Uptime Robot
- Have the “Crypto” setting as “Flexible” in Cloudflare
How to make the custom config?
That is so easy:
- Login to your Cloudflare account
- Click the domain of your status page
- Click “Page Rules>Create Page Rule”
- Enter *MyStatusPageCustomDomain* (like *status.mydomain.com*) into “If the URL matches” field
- Click “Add Setting>SSL>Full”
- Click “Save and Deploy”
- That’s it.
And, here is a screenshot of the setting:
For HTTP monitors, Uptime Robot considers them as up or down according to the HTTP statuses returned (or if “no response returns at all”).
If the HTTP status returned is:
- between 200 and 399, it is considered as “up”
- bigger than 399, is considered as “down”
- with an exception:
- equals 401 and no authentication info is defined, it is considered as up
- equals 401 and authentication info is defined, it is considered as down
It is now possible to customize which HTTP statuses are considered as up or down.
This is pretty handy if you plan to monitor a web page which returns HTTP 404 and want it to be detected as “up”, prefer to ignore several erroneous HTTP statuses and more.
The feature is available in the Pro Plan and can be reached from the “Add/Edit Monitor dialogs of HTTP monitors>Advanced Settings>Custom HTTP Statuses tab”.
Uptime Robot, by default, sends all HTTP requests with pre-defined HTTP headers.
Now, it is possible to customize this totally with the “Custom HTTP Headers” feature that can be found in the Pro Plan’s “Add/Edit Monitor Dialog>Advanced>Custom Headers” option.
Sample use cases:
- For monitoring the mobile version of a web page, we can use a mobile “User-Agent” header to force the site to serve the mobile content.
- The site may be requiring/expecting various authorization HTTP Headers
- We may want to white-label the requests and change the User-Agent to a custom one
Hope it helps for a better monitoring :).