Bulk Edit for Checks

Many of our customers have requested the ability to edit a large amount of checks at once. Previously, we have suggested using the API to edit checks, and while that still is a good option, we are glad to announce that we have enabled bulk check editing on our website as well. *Throws party* *Throws confetti* *Throws spaghetti*

Bulk Edit ScreenshotSigning into your account at https://nodeping.com/login.html will bring you to the homepage, where you can simply tick off the checks you want to edit, or check off the box at the top next to “Type” to select every check currently displayed on the list at once.

Then press “Bulk Edit”, next to the “Check Status” and “Add new check” button. If you forget to select any checks before pressing “Bulk Edit”, a pop-up will gently but firmly and lovingly remind you tick the checkboxes.

For Bulk Edits the dialog will show settings that you can set on all of the checks you selected.  Only check properties that are common for the selected checks are shown. As a result, you’ll typically have the ability to modify the most properties if the checks you have selected are all of the same check type.

Some fields in the Bulk Edit dialog may say “[Various Values]”.  Leaving these fields as they are will leave all of the checks you’re editing with their individual values for that field.

One important thing to note is that changing notifications will change all of the notification settings on all of the checks to whatever you set in the dialog.  This isn’t additive, so it doesn’t merge different notification settings. It replaces the existing notification settings with the notifications you select in the Bulk Edit.

After you have changed the checks, press “save” and the checks will be automatically updated with your changes.

Hopefully you will find Bulk Edits helpful. To contact us, email us at support@nodeping.com. If you don’t have a NodePing account, you can sign up for our free 15-day trial by clicking the link.

 

Import Script for NodePing

Moving your uptime monitoring to NodePing is now even easier.

We have a fresh Node.js script that will import your checks from Pingdom, StatusCake, or Uptime Robot. *

The script will create contacts, checks, and configure notifications in NodePing to match your current provider.

The script and instructions on how to implement it can be found on our GitHub page. Some services don’t map to NodePing’s features very well so be sure to look at the known limitations section.

If you don’t see your current provider supported by our import script, please let us know and we’ll do our best to get it added.

Don’t have a NodePing account yet? You can sign up for a free, 15-day trial at https://nodeping.com

* service names are trademarked and belong to their respective owners.

Probe Server Changes [AU, AZ] Removal [CH, MO] and Addition [PL]

The following probe servers will be changing IP addresses on 2018/06/06:

Phoenix, Arizona (AZ) – USA is changing from
(104.245.105.2 / 2602:ff97:0:2:225:90ff:fee5:b89)
to
(107.152.108.14 / 2607:f7a0:1:2:225:90ff:fee2:42da)

Sydney, Australia – AU is changing from
(103.25.58.108 / 2406:d501::3f02:2574)
to
(139.99.130.48 / 2402:1f00:8100:230::10)

We’re also adding a new probe to the European region on 2018/06/06:
Warsaw, Poland – PL
(217.182.201.227 / 2001:41d0:602:4e3::10)

The following probes are being removed on 2018/06/06:

Kansas City, Missouri (MO) – USA
(63.141.244.242 / 2604:4300:a:9d:202:c9ff:fec0:da0e)

Zurich, Switzerland (CH) – CH
(5.102.145.51 / 2a06:c01:1:1102::9133:51)

Please adjust your firewalls appropriately if you whitelist so your checks do not fail because of the probe IP address changes.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ, a text file, and via DNS query, probes.nodeping.com.

 

[UPDATE – 2018-06-06 13:20GMT-6] – IP changes and probe addition complete.

Telegram Notifications

This post will provide instructions on how to get NodePing notifications via Telegram using NodePing Webhooks and Telegram Bots.  Webhooks are available in our Business and Provider plans.

The Telegram Bot system is very useful for integrating with Telegram. Nodeping webhooks work seamlessly with the Telegram Bot to send ‘down’ and ‘up’ notifications. It’s a great alternative to SMS that is also cross-platform.

First, you will need to set up a Telegram account for yourself if you haven’t already. This can be done by getting the app on your mobile device or computer (there are Windows/macOS/Linux clients, as well as unofficially supported for FreeBSD). A working phone number will be required to set up an account.

Next, you need to create your own Telegram Bot.  To do this, you’ll have to to chat with Telegram’s own BotFather (a bot that creates other bots – the end is nigh!) You can find it by typing “@BotFather” into the user search bar in Telegram. Once you have started a chat with it, you will be prompted with a message from the BotFather.

Create your own bot by simply typing “/newbot” and following the instructions that are given. Here is a screenshot of what setting up a new bot setup looks like:

That long token is important.

Now that you have your new Telegram Bot and token, you’ll need to get the ChatID for the user or channel you want to send notifications to. This can be done by starting a chat with your new bot inside Telegram. You would start the chat like you did with BotFather, by typing in @nameofyourbot followed by sending “/start” to the bot. With that done, you can get the ChatID by visting the URL that shows your bot’s updates.  That URL will look like:

https://api.telegram.org/bot<your-secret-bot-token>/getUpdates

Plop that in your browser and you’ll get back some text – JSON formatted text.

The reply is the updates for your Telegram bot, which should only include the chat your telegram user started with the bot a few seconds ago. Look through the JSON response for the ChatID. It will be a random looking number thing.

Now that you have the ChatID, you’ll need to configure a new Webhook in NodePing. Log in and go to the Contacts tab. Add a new contact and give it a name – like “Telegram Bot”. Select the “Webhook” notification type and change the action to “POST”. Enter the following value in the URL field (replacing <your-secret-bot-token> with… you know, your bot token):

https://api.telegram.org/bot<your-secret-bot-token>/sendMessage

Next, in the Headers section add a new key called “Content-Type” and the value of “application/json”. It should look like this:

Then click on the the Body section.  In the text area, you need to add the following JSON.

{“chat_id”:<your-ChatID>,”text”:”NodePing: – {label}: {type} is {event}”}

Then save your newly minted webhook.  It’s ready to be added to the notification section of your checks.

Now you can receive NodePing notifications via Telegram!

Your alerts will look something like this.

Telegram bots have a lot more functionality that you can read about.  NodePing webhooks can also do a lot more, like templating and conditional statements, which you can read about.

If you need help getting things working right, please let us know at support@nodeping.com.  If you don’t yet have a NodePing account, please sign up for our free 15-day trial.

Probe Server Changes [NY] and Addition [MO]

The following probe servers will be changing IP addresses on 2018/05/09:

New York City, New York (NY) – USA is changing from
(168.235.67.200 / 2604:180:2:38f::928a)
to
(66.23.202.26 / 2605:9f80:c000:127::2)

We’re also adding a new probe to the North America region on 2018/05/09:
Kansas City, Missouri (MO) – USA
(63.141.244.242 / 2604:4300:a:9d:202:c9ff:fec0:da0e)

Please adjust your firewalls appropriately if you whitelist so your checks do not fail because of the probe IP address changes.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ, a text file, and via DNS query, probes.nodeping.com.

 

[UPDATE – 2018-05-09 19:00GMT-6] – IP changes and probe addition complete.

Update to TOS and Privacy Policy – NodePing and GDPR

Part of the benefit of being a relatively small distributed company in the Internet cloud age is that we can have a global reach without requiring a lot of infrastructure and overhead. We have customers all over the world, but we have almost no presence anywhere beyond our home office. Our people can work from anywhere with a good Internet connection. Since we work in the cloud, most of our computer systems are in places we have never been. We don’t even handle payment information directly in any of our workplaces. Payment information is passed directly to our payment processors. Working in the cloud age helps all of this work smoothly and safely with very little physical infrastructure required.

The downside of all of that is that our customers are all over the place, including legal jurisdictions all over the world. The regulatory world hasn’t really caught up with the idea of cloud based distributed companies. We want to comply with all applicable requirements, but understanding what requirements apply to us in various locations isn’t always easy.

The GDPR has brought this challenge front and center for us. We do not have any actual presence in any European countries. However, we do have customers in nearly all European countries, and are subject to some data privacy protections where those customers are located. That makes sense, and we want to be good citizens, but as with many other Internet based companies it can be daunting to figure out how the regulations apply to us.

Fortunately for us, the principles established in the GDPR are principles that we were already following in our normal practices. Our customers are businesses and providers of Internet based services, and for the most part we don’t provide services to individual end users. Additionally, our customers manage their own data, have full access to the information in our systems, and we don’t process or use the information they set up in our service beyond what they configure for their own use.

We did find that there were a few requirements related to the GDPR that, while our prior practices were basically already in compliance, weren’t clearly articulated in our Terms of Service or Privacy Policy. So, we’re updating both documents to more clearly set out how our policies and practices address these areas.  The updates will take effect on 2018-05-18

This includes more clearly stating that we are not collecting or processing data beyond what our customers configure to use for their monitoring. We only use contact information in our system to provide the monitoring you configure, and send the notifications you set up in the way you configure them. Our customers can download their own data whenever they want to. Beyond that, we don’t use or process information from our customers.

This is our normal practice, and applies to everyone. We don’t maintain a separate policy for customers in Europe.

Since we are a data processor, and the data is under the control of our customers who are themselves businesses providing services to others, for GDPR purposes we are a Processor rather than a Controller. Since we don’t have a presence in any EU countries, and we provide processing services to controllers in several EU countries, according to the guidelines published by the Article 29 Working Party, the lead supervisory authority will be the supervisory authority that is competent to act as lead for the controller.

If you are a data controller in a European country, or even if you aren’t, you may have questions about our systems that are necessary for you to comply with obligations you have in your location, and for your customers. If you have questions or concerns that aren’t addressed in our updated policies, please let us know.


UPDATE: We have now received our Privacy Shield certification, which required our Privacy Policy to be updated again to meet those requirements.   The most recent changes are aimed specifically at the certification requirements.  As always, you can see our current Privacy Policy and our Terms of Service on our web site.

Probe Server Changes [PY,NC]

The following probe servers will be changing IP addresses on 2018/04/03:

Cary, North Carolina (NC) – USA is changing from
(104.225.1.48 / 2607:fc50:0:15::3a0)
to
Charlotte, North Carolina (NC) – USA
(192.154.255.88 /2604:9980:0:12c:ec4:7aff:fecb:776c)

Philadelphia, Pennsylvania (PY) –  USA is changing from
(154.16.159.242 / 2604:bf00:210:1d::2)
to
(208.82.130.170 /2604:bf00:214::10)

Please adjust your firewalls appropriately if you whitelist so your checks do not fail because of the probe IP address changes.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ, a text file, and via DNS query, probes.nodeping.com.

 

[UPDATE – 2018-04-03 11:35GMT-6] – IP changes complete.