Site update and feature releases Oct 2016

We’ve rolled out some UI and feature updates for NodePing today. We hope you find them helpful. I’ll summarize the changes here. Look here for future posts, which will go into more details for each.

Delayed Notifications:
You can now set a delay on ‘down’ alerts. This will help make your notifications more actionable for frequently flapping services. This new feature can also be used to escalate alerts or notify support/management if services remain offline. This feature has been available for a while in our API, but hasn’t been in our documentation, and has now been added to our UI as well. See the ‘Delay’ drop down in the Notification section of your check.

Check Cloning:
You can now clone an existing check, with all its settings, in our UI to create a new check. This will help reduce “clickty-clickty” syndrome when setting up a lot of checks with similar settings. Click on the label of the check you want to clone to display the details to reveal the ‘Clone Check’ link on the far right.

Notification Dependencies:
When an edge router or server fails, it’s assumed that all the services that depend on them will also fail. It’s not helpful to receive hundreds of alerts for dependent services. You can now set another check as a notification dependency on each check. If the dependent check is already failing, notifications will be suppressed. Use this to avoid alert floods when bottleneck services fail. You can find the ‘Dependency’ drop down in the Notification section of each check.

Disable All Notifications:
There is now a link in the Contacts tab to “Disable notifications”. Use this to suppress all alerts until you re-enable them using the same link. It’s another way to help avoid the distraction of alert floods during big outages.

Disable Checks:
Now you can disable multiple checks with one click. You’ll find the “Disable All Checks” link in the Account Settings – General Settings tab. You can also apply filters based on label, target, or check type to, for example, disable all PING checks or all checks pointing to “example.com”. Use this to disable checks during planned outages/maintenance or to quiet down your logs when troubleshooting.

All the above new features, except check cloning, are also available via our API. If you have any questions about these new features, reach out to support@nodeping.com; we’re happy to help.

Probe Server Changes – [UT,RO,FL,AM]

The following probe servers will be changing IP addresses on 2016/10/04:
Ogden, Utah USA(UT) will change from 192.154.111.10 to 192.154.102.130
Bucharest, Romania (RO) will change from 77.81.108.115 to 89.45.10.135
Miami, Florida (FL) will change from 107.161.178.251 to 162.254.202.35

We’ll also be adding the following new probe in our East Asia/Oceania region on 2016/10/04:
Melbourne, Australia (AM) will be added – 103.207.28.11

We’ll also be removing the following probe in our Latin America region on 2016/10/04:
Curico, Chile (CL) will be removed – 190.114.254.203

Please adjust your firewalls appropriately 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

Edit 2016-09-28 – Fixed the incorrectly listed the current IP for the Florida probe FL.

[UPDATE – 2016-10-04 23:15GMT-4] – changes complete.

Probe Server IP Address Change – [NC]

Our probe in North Carolina, USA will be changing IP addresses on 2016/8/9:
North Carolina (NC) is changing from 192.111.152.6 in Lenoir to 104.225.1.179 in Cary.

We had some trouble with the previous data center in Lenoir.  It was intercepting all our SMTP checks causing some SMTP services to appear up when they were really down.

Please adjust your firewalls appropriately so your checks do not fail because of the probe IP address change.

An always current and updated list of all the IP addresses for our probe servers can be found in the FAQ

[UPDATE – 2016-08-09 09:56GMT-4] – IP change complete.

Probe Server IP Address Changes and Additions – [FL,SG,UT,NC]

The following probe servers will be changing IP addresses on 2016/6/6:
Singapore (SG) will change from 191.101.242.137 to 103.25.202.111
Miami, Florida USA (FL) will change from 192.157.238.128 to  107.161.178.251

We’ll also be adding the following new probes in our North America region on 2016/6/6:
Lenoir, North Carolina USA (NC) – 192.111.152.6
Ogden, Utah USA(UT) – 192.154.111.10

Please adjust your firewalls appropriately 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

[UPDATE – 2016-06-06 10:56GMT-6] – IP changes and additions complete.

IPv6 Monitoring

NodePing now supports IPv6… mostly.

Our website and server monitoring service can now monitor IPv6 services. With real, honest-to-goodness ICMP pings as well as the funky bracket notation for URLs:

http://[2606:c700:4020:11::53:4a3b]/

Our IPv6 support is pretty extensive.

Even though IPv6 adoption has only just crossed the 10% mark, we know many of our customers are out in front of that pack and we’re happy to keep an eye on your v6 stuff.

If you’re using hostnames that resolve to both IPv4 and IPv6, you’ll need to set up separate checks and specify the IPv6 services using the IP as our services will continue to prefer IPv4 for resolution of hostnames. The exception here is our ping check, where you can specify the protocol version to use with a hostname.  You’ll need two checks to cover both protocols.

Unfortunately there are a few caveats and addendums… A couple of our check type don’t yet support IPv6 routing – RBL and SIP checks.  Not many RBLs (Real-time BlackLists) support IPv6 addresses and our SIP check relies on a library that doesn’t support IPv6.  We’ll keep an eye on these and add IPv6 support to them when we can.

We also aren’t able to provide IPv6 monitoring from our Latin America region, sorry.  IPv6 connectivity in Latin America is nearly non-existent currently. We’re sure that will change in the future and we’ll be able to bring that online eventually as providers there start offering it. Our other regions (North America, Europe, and East Asia/Oceania) are well supported.

IPv6 support is available on all NodePing plans. If you’ve got IPv6 services that need monitoring and don’t have a NodePing account yet, please sign up for our free 15-day free trial.  We’ve got your back.

 

Slack notifications

By popular request, we’ve rolled out support for notifications via Slack.

Setting up your NodePing account to send notifications to Slack is easy.  Just set up an incoming webhook in your Slack account and put the webhook URL into your ‘Slack’ notification contact in NodePing.  Then you can assign that contact to your checks to receive ‘down’ and ‘up’ messages on your configured Slack channel.

Notifications through Slack are available on ‘Business’ and ‘Provider’ plans.

Let us know what notification types or features you’d like to see next.

Probe Server IP Address Change and Addition – [RO,SE,HU]

The following probe server will be changing IP addresses on 2016/3/9:
Bucharest, Romania (RO) will change from 89.45.249.16 to 77.81.108.115

We’ll also be adding the following new probe in our Europe region on 2016/3/9:
Goeteborg, Sweden (SE) will be added – 185.86.148.18

We’ll also be removing the following probe in our Europe region on 2016/3/9:
Budapest, Hungary (HU) will be removed – 213.181.208.18

Please adjust your firewalls appropriately 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

[UPDATE – 2016-03-09 10:44GMT-7] – IP change and addition for SE complete.