Cluster Check

Allow me to introduce our newest check type, Cluster.

The Cluster check allows you to group interdependent NodePing checks in order to get notifications and track availability of the group of checks as a whole. You specify a threshold of how many of those checks must be passing in order for the cluster to be considered ‘up’. If the number of those checks passing drops below your configured threshold, the cluster check will fail and send the configured notifications.

We use it to keep an eye on our Cassandra servers but you can use it for any logical group of services that are interdependent. Some other use cases:

  • DNS services – monitor each DNS server with DNS checks and then a cluster check on those DNS checks to get that very important alert when all DNS servers are offline!
  • Web servers – monitor the backend web servers behind your reverse proxy or load balancer to make sure you have enough of them available to handle the traffic.
  • SMTP – monitor your SMTP checks and know that there’s always at least one server available to receive email for your domains.

Cluster checks are available to all NodePing plans today. If you’re not using NodePing yet, please sign up for our 15-day, free trial today.

 

Banana image Designed by Daviles / Freepik

Probe Server Changes and Addition [IT,UK,CH,JP,CA,OR,GA]

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

Manchester, England (UK) – GB is changing from
(194.187.248.8 / 2001:ac8:21::b0)
to
(185.116.237.211 / 2a06:8181:a0:bfaf::1)

Tokyo, Japan (JP) – JP is changing from
(106.186.116.86 / 2400:8900::f03c:91ff:fedb:b594)
to
(180.149.230.17 / 2406:d500:9::7a91:9b75)

Los Angeles, California (CA) – USA is changing from
(184.170.243.202 / 2607:f7a0:3:8:225:90ff:fe51:d0b0)
to
(192.161.172.202 / 2607:fcd0:106:ab01::10)

Portland, Oregon (OR) – USA is changing from
(69.163.39.244 / 2605:ea00:1:1:d267:e5ff:fee7:51c)
to
(100.42.30.2 / 2604:B480:FFF6::10)

Atlanta, Georgia (GA) – USA is changing from
(66.71.251.162 / 2607:f7a0:6:a:225:90ff:fe79:4318)
to
(107.150.22.26 / 2607:fcd0:aa80:2200::10)

We’re also adding a new server to the Europe region on 2017/12/05:
Zurich, Switzerland (CH) – CH
(5.102.145.51 / 2a06:c01:1:1102::9133:51)

The following probe is being removed on 2017/12/05:
Milan, Italy (IT) – IT
(185.93.183.12 / 2001:ac8:24::40)

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 – 2017-12-05 10:53GMT-7] – IP changes and probe addition/removal complete.

WHOIS Monitoring

Need an alert when your domain is about to expire?

Want to make sure your domain admin contact hasn’t been tampered with?

Need a notification when your configured name servers get changed?

Maybe you’re running your own TLD (you lucky dog, you) and need to verify your WHOIS servers are up and responding properly?

NodePing’s new WHOIS monitoring has got you covered. Our new check will verify the presence or absence in the WHOIS response for any text you specify, helping you ensure your domain information hasn’t been hacked or altered without you knowing.  We’ll also send alerts before the domain expires. You choose how many days ahead of expiration you want to receive the notifications and how you want to be notified (email, SMS, Voice call, Pushover, Slack, etc)

You can optionally configure a specific WHOIS server to query via IPv4 or IPv6.

WHOIS checks are available to all NodePing accounts starting today. If you don’t have an account yet, sign up for your free, 15-day trial today and let NodePing keep an eye on your WHOIS info for you.

Probe server change [SG]

The following probe server will be changing IP addresses on 2017/10/18:

Singapore (SG) – SG is changing from (103.25.202.111 / 2400:c980:0:2:48d:a4ff:fe01:1262) to (103.16.16.30 / 2001:df0:24f:214::10)

Please adjust your firewalls appropriately if you whitelist 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 – 2017-10-18 11:45GMT-6] – IP change complete.

Probe Server Change and Addition [FR,MX]

The following probe server will be changing IP addresses on 2017/09/19:

Paris, France (FR) – FR is changing from (37.59.86.248 / 2001:41d0:a:7a50:5:5:9ab9:a412) to (195.154.167.97 / 2001:bc8:2327:110::10)

We’re also adding a new probe to the Latin America region on 2017/09/19:
Mexico City, Mexico (MX) – MX (138.204.171.109)

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

[Update 2017-09-18] – the new probe planned for Mexico will not be added as planned.

[UPDATE – 2017-09-19 10:41GMT-6] – IP change complete.

Creating Clones

Have you ever wanted to be an evil genius and create a clone army to take over the universe? Well, we can’t help you with that but we do have a “Clone Check” feature. It might not take over the universe, but it can be a great time-saver.

ca

When you want to create a check that is similar to one you already have, you can use our “Clone Check” feature to create a new check based on the settings of an existing check. You can then change whichever fields you choose, such as the URL or check type, as well as the label. This saves you from having to type in the various fields over and over or set complicated notifications, delays, etc, when you already have a similar check ripe for cloning.

To clone a check, log into your NodePing account, and go to the “Checks” tab. Click on the label for the check you want to duplicate to open the information drawer. On the lower right, there are a list of links, including “Clone Check”. Clicking on it will bring up a new dialog for the cloned check with all of the values preset based on the check you are cloning. You can change the fields to fit the new check you want. Then click “Save” at the bottom of the dialog.

Who knows? If you create enough, maybe you can take over the universe.

Probe Server Changes [AZ,CO]

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

Phoenix, Arizona (AZ) – AZ is changing from (162.253.177.250 / 2602:fff6:5:fba3::baa6) to (104.245.105.2 / 2602:ff97:0:2:225:90ff:fee5:b89)
Denver, Colorado (CO) – CO is changing from (162.211.64.212 / 2602:fff6:d:e301::10fe) to (173.248.161.42 / 2607:fc88:100:40::2)

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

[UPDATE – 2017-07-06 10:30GMT-6] – IP changes complete.