Probe Server Changes [IL]

The following probe server will be changing IP addresses on 2018/11/14:

Chicago, Illinois (IL) – USA

(104.128.57.130 / 2607:f128:4a:16::10)
to
(162.212.158.87 / 2607:9000:0:35::1f54:9bad)

 

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-11-14 12:35GMT-6] – IP change complete.

WHMCS Module Update

Fresh update for our WHMCS module.  Changes include:

Use our WHMCS module to add NodePing uptime monitoring to your hosting/server offerings.

Get the new module file here.

Probe Server Changes [LD, OR], Removal [AZ, KS, NC, OT] and Region Change [FL]

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

London, England (LD) – GB
(5.2.16.148 / 2a00:e740:1:27::65c3)
to
(5.226.139.158 / 2a01:4020:1:26::10)

Portland, Oregon (OR) – USA
(100.42.30.2 / 2604:B480:FFF6::10)
to
(162.210.173.188 / 2604:b480:ffff:ffff:fa06::10)

 

The following probe servers will be removed on 2018/09/05:

Phoenix, Arizona (AZ) – USA
(107.152.108.14 / 2607:f7a0:1:2:225:90ff:fee2:42da)

Kansas City, Kansas (KS) – USA
(172.86.180.18 / 2604:5800:0:42::2)

Charlotte, North Carolina (NC) – USA
(192.154.255.88 /2604:9980:0:12c:ec4:7aff:fecb:776c)

Ottawa, Ontario (OT) – CA
(199.167.130.19 / 2605:2100:0:1::7b03:9072)

 

The following probe server will be included in the North American Region on 2018/09/05:

Miami, Florida USA (FL) – US
(162.254.202.35 / 2604:bc80:8001:3c:225:90ff:fee5:5c6)

 

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-09-05 14:24GMT-6] – IP changes and probe addition complete.

PUSH Checks – Heartbeats and Metrics Monitoring

One of the most requested features we get is the ability to push monitoring results into NodePing. Today, we make good on all those requests and are happy to announce our latest check type, PUSH.

Unlike our other checks, PUSH checks allow your server to push metrics into our system, track the metrics, and receive alerts based on the results. This significantly adds to your ability to monitor services that are not Internet accessible, and monitor additional custom metrics. Our customers running LANs can now get heartbeats and metrics on internal servers like Windows AD controllers. Or, you can monitor metrics that are only relevant to your systems in ways that are specific to your environment. We’ll track and alert on any metric you want to push at us!

Heartbeats and Metrics

PUSH checks are configured to send results on a specific interval and you can configure the check to fail if we haven’t received a pushed result from you. This is the heartbeat functionality.

You can also push us a data payload of metrics with the PUSH check result and configure your check to track those metrics. The check will fail if any configured metric is missing or if the values in the result are outside your configured min/max range.

Metrics are great for keeping an eye on system load, disk free space, or any other service or system metric you can gather on a server and send to us.

PUSH checks are flexible and can be configured to be heartbeat-only, metrics-only, or both.

PUSH Clients

To send us your result (heartbeat or metrics), you’ll need to submit an HTTP POST to NodePing with information about the check and optionally the metrics. Details can be found in our in our PUSH check documentation.

We’ve got fully-functional, open-source clients in Python2, PowerShell, and POSIX script available on our GitHub public repo that have been tested with the following OSes:

  • CentOS 5 (Python2 and POSIX)
  • CentOS 6 (Python2 and POSIX)
  • CentOS 7 (Python2 and POSIX)
  • Debian 9 (Python2 and POSIX)
  • Devuan 2 (Python2 and POSIX)
  • Fedora 28 (Python2 and POSIX)
  • FreeBSD (Python2 and POSIX)
  • OpenBSD 6.3 (Python2 and POSIX)
  • OpenSUSE LEAP 15 (Python2 and POSIX)
  • Raspbian STRETCH (Python2 and POSIX)
  • Ubuntu 14.04 (Python2 and POSIX)
  • Ubuntu 16.04 (Python2 and POSIX)
  • Ubuntu 18.04 (Python2 and POSIX)
  • Windows server 2012 (Python2 and powershell)
  • Windows server 2016 (Python2 and powershell)

Download a client and follow the instructions in the client README.md file to set up your PUSH client.

An example of the default metrics sent from our POSIX client:

OS load: 1 minute, 5 minute, and 15 minute load stats
Memory free in MB
Disk space free in percentage by mount point.

There are also optional modules for Redis, Cassandra, ZFS, iptables, and more.

All our clients are built so you can add your own modules to push additional metrics – the ones you care about. The requirements for pushing metrics into our system are fairly simple, so you can write your own scripts in your preferred language. It just needs to output JSON data with numeric values. You can find the information you need to create your own client modules in our PUSH check documentation and take a look at existing modules for examples.

We encourage pull requests for new modules so if you build something you think others would find useful, please do share.

We’re working on new reports and dashboards to visualize metrics, making the new PUSH check even more useful, so keep an eye out here on the blog for those announcements.

If you aren’t using NodePing yet, you can sign up for a free, 15-day trial and test out our new PUSH checks yourself. We think you’ll love the new functionality along with our rock-solid monitoring and fast/accurate notifications.

Probe Server Addition [AM]

The following probe server will be added on 2018/08/07:

Melbourne, Australia (AM) – AU
(144.48.37.241 / 2404:f780:2:950:216:3cff:feb8:ab8e)

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-08-07 16:15GMT-6] – the addition of the new probe is now complete.

Twitter notifications to stop working on 2018-08-15

Twitter API changes set for August 16, 2018 will result in NodePing no longer being able to reliably send direct message notifications. The new API endpoint allows only 5 DMs per user per 24 hours. If you’d like to receive NodePing notifications via direct message, please consider letting twitter know how these changes affect you.

NodePing has many other notification methods available.

Probe Server Changes [DE] and Removal [AM]

The following probe will be removed on 2018/07/12:

Melbourne, Australia (AM) – AU
(103.207.28.11 / 2404:2780:0:1::21)

The following probe server will be changing IP addresses on 2018/07/12:

Frankfurt, Germany (DE) – DE

(5.1.70.107 / 2a00:f820:26::10)
to
(54.36.110.96 / 2001:41d0:700:1360::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-07-12 17:30GMT-6] – IP changes and probe removal complete.