PUSH Client Wizard

2019/06/07 by Leave a comment

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.

Filed under Announcement, PUSH, SysAdmin Tagged with , ,

Check for Silence in Audio Streams

2019/05/23 by Leave a comment

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.

Filed under Announcement, audio, NodePing Updates Tagged with , , , ,

Probe Server Change [WA]

2019/05/22 by Leave a comment

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.

Filed under Announcement, IP Change Tagged with ,

Probe Server Changes [IL]

2019/04/17 by Leave a comment

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.

Filed under Announcement, IP Change Tagged with ,

Probe Server Changes [UK]

2019/01/09 by Leave a comment

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.

Filed under Announcement, IP Change Tagged with ,

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

2018/12/05 by Leave a comment

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.

Filed under Announcement, IP Change Tagged with , , ,

Probe Server Changes [IL]

2018/11/07 by Leave a comment

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.

Filed under Announcement, IP Change Tagged with ,

WHMCS Module Update

2018/10/18 by Leave a comment

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.

Filed under Announcement, WHMCS Tagged with ,

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

2018/08/29 by Leave a comment

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.

Filed under Announcement, IP Change Tagged with , , , , , , ,

PUSH Checks – Heartbeats and Metrics Monitoring

2018/08/27 by Leave a comment

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.

Filed under Announcement, NodePing Updates, PUSH Tagged with , ,

← Older posts

Newer posts →