Probe Server Addition [PE]

The following probe server will be added on 2019/07/10:

Perth, Australia (PE) – AU
(203.29.240.44 / 2404:9400:4:0:216:3eff:fee1:3c1b)

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

PUSH Client Wizard

Last year, we introduced a new feature called PUSH Checks. This check type allows your server to push numeric metrics into our system, track the metrics, send a heartbeat, and receive alerts based on the results. This is a powerful tool, and we use it internally at NodePing to monitor system load, backup processes, gather metrics from logs, and a variety of other things. We’re also glad to hear about customers using this feature in interesting ways as well.

However, until now setting up a PUSH check could be challenging. You would have to create the check, download a copy of the client and configure it with the Check ID and Checktoken as well as configure the metrics. So today we’re releasing a PUSH Client Wizard (available on GitHub) that makes PUSH Checks really easy to configure and deploy across your systems using an interactive command line wizard. This Python 3 client is able to run on any system with Python 3.5 or newer, and has been tested on Linux, Windows 10, and FreeBSD.

Features

So what can it do? The wizard lets you list your existing PUSH checks, create new PUSH checks, and delete PUSH checks you no longer want.

When listing checks, it will show information such as:

  • Your check’s label
  • ID
  • Checktoken
  • If the check will fail when its results are old
  • PASS/FAIL status
  • If it’s enabled/disabled
  • Run Interval

When creating a check you can configure all sorts of information for the check such as:

  • The client you will use (POSIX, Python, Python3, PowerShell)
  • Information about the check (Label, interval, enabled, public reports, fail when old)
  • Metrics to gather for the check (or none for basic heartbeat functionality) and values for pass/fail
  • Contacts and their notification schedules
  • Client configuration
  • Remote/local deployment

Configuring the client is an optional step if you want to do it yourself. When configuring the client, you have the ability to deploy the new PUSH check client locally or remotely over SSH! Once the client has been configured, a cron job or Windows Task Scheduler event information will be provided so you can simply copy/paste the provided information at the end.

This tool will allow you to quickly and easily manage your PUSH checks so you can monitor your systems with PUSH checks in less time.

Give the wizard a try today!

We encourage pull requests for new features so if you make changes you think others would find useful, please do share.

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 and give the new wizard a try.

Check for Silence in Audio Streams

We’re happy to announce a new volume detection feature for audio streams.

Our AUDIO check is great at making sure your stream is up and running but until this update we didn’t have a way to tell if the audio playing was dead air. Silence detection is an important part of providing audio streaming and NodePing can now send you notifications if your Internet radio, podcast, or other audio stream is playing silence instead of your content.

Our volume detection samples 10 seconds of your stream and computes an average decibel level of the audio. If that detected volume level is lower than your configured threshold (-90 to 0 with a default of -45) your AUDIO check will fail and you’ll receive any configured alerts.

Dead air detection takes more resources (CPU, RAM, bandwidth) so the new feature is only available in our “Provider” plan.  If you’re a current NodePing customer and would like to try it out, please let us know and we can provide a temporary free upgrade for you to kick the tires. If you don’t yet have a NodePing account, please sign up for our 15-day, free trial and then go to the billing section and upgrade your trial (still free) to a “Provider” plan to get access to the new feature in your AUDIO checks.

For more information check our AUDIO check documentation or contact us. We’d love to hear what you think of the new feature and what you’d like to see next.

Probe Server Change [WA]

The following probe server will be changing IP addresses on 2019-05-29:

Seattle, Washington (WA) – USA

(107.161.26.116 / 2604:180:1:2d0::e5c9)
to
(173.205.92.154 / 2607:fcd0:cd00:a00::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 – 2019-05-29 09:00GMT-6] – IP change complete.

Probe Server Changes [IL]

The following probe server will be changing IP addresses on 2019-04-24:

Chicago, Illinois (IL) – USA

(162.212.158.87 / 2607:9000:0:35::1f54:9bad)
to
(96.9.222.119 / 2602:ffc8:3d02::190:4ae6)

 

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 – 2019-04-24 13:26GMT-6] – IP change complete.

Probe Server Changes [UK]

The following probe server will be changing IP addresses on 2019/01/16:

Leeds, England (UK) – GB
(109.75.172.133 / 2a00:f9c0:0:405::12)

to

Rugby, England (UK) – GB
(78.157.200.148 / 2a01:a500:375:1::25:4617)

 

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 – 2019-01-16 13:10GMT-6] – IP change complete.

Probe Server Changes [TX, AR] and Removal [SE]

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

Goeteborg, Sweden (SE) – SE
(185.86.148.18 / 2a02:7aa0:1619::4b6a:706a)

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

Dallas, Texas (TX) – USA

(45.58.61.34 / 2604:6600:2000:c::2)
to
(198.96.95.50 / 2607:fcd0:da80:4300::10)

Federal, Argentina (AR) – AR

(190.12.101.90)
to
(190.210.176.48)

 

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-12-12 15:08GMT-6] – IP changes and probe removal complete.