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 “”. 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; we’re happy to help.

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.

NodePing mobile push notifications to wake you up!

We’re pleased to announce another new notification type for NodePing server monitoring. You can now receive persistent push notifications through Pushover on your iOS or Android device.

Once configured, each ‘down’ event for your check will push an ’emergency’ notification to your device and automatically re-alert every 30 seconds until it is acknowledged, up to 5 minutes.  Try sleeping through that!

Pushover notifications are faster and more reliable than SMS and are currently the only NodePing notification type that will persistently re-alert you when a check fails. Please consider switching your SMS alerts to Pushover alerts. It will also help us keep NodePing prices down as Pushover alerts are significantly cheaper than international SMS.

Once installed, simply add your Pushover ‘user key’ as a ‘Pushover’ notification type in your contact record and select that key when creating or editing a NodePing check.

For those who may be interested in viewing your check status in a native iOS app, one of our customers has created HostCheck using our API.

Let us know in the comments what NodePing feature you’ve been itching to see.

How to integrate PagerDuty into NodePing

Many of our customers are also big PagerDuty fans. What’s not to like! PagerDuty offers great escalation and on-call hand-off capabilities as well as flexible voice, sms, and even pajama alerts.

To make it easier for you to integrate your already existing PagerDuty workflow, we’ve added a new contact notification type to NodePing. The ‘PagerDuty’ type accepts a ‘Service API Key’. You can find information on how to set up a PagerDuty generic API service at their support site.

Our system will send a ‘trigger’ event on each failure and a ‘resolve’ event on each recovery. Add an entry in your contact record by specifying your PagerDuty ‘Service API Key’ (they kind of look like a big random string “47b3a13848514c3fa3def842464eeaa8”) and selecting ‘PagerDuty’ in the notification type drop down. Then specify that contact when you edit or create your NodePing checks.


You can specify as many different PagerDuty contacts as you like. This allows you to use multiple ‘Services’ with NodePing and have full control of your PagerDuty escalations and notifications.

We strive to bring you the best solutions for your monitoring needs. We’ve set our eyes on Android and iOS push notifications next so follow this blog for that notification. We’d also love to hear from you. What notification types or other features would you like to see in NodePing?

If you’re not a NodePing customer yet, you can sign up for a free 15-day trial and kick the tires for yourself. We’re confident you’ll like what you find.

Webhook Notifications

We’re glad to announce the addition of a webhook notification type to NodePing.

Webhooks allow you to configure our service to hit a URL when a server goes down and when it comes back up. You can configure webhooks to automate actions when a service fails or comes back online. Common uses include changing DNS settings when a server goes offline and restarting a database when it fails.

Webhooks are available as a notification type for contacts. Create a new webhook by adding a line to the contact with the full URL as the ‘address’ and select ‘webhook’ as the type. You can then add the webhook to the notification section of any of your checks.

The webhook sends an HTTP GET request to the URL you specify. You can add basic authentication and a query string in the URL. Additional information about the check, the result, and the event (up,down,first) will be injected into the query string as well. For a full list of the fields passed to webhooks, see our documentation.

Webhook notifications are now available on all Provider plans. If you’d like to use webhooks but are currently on a different plan, you can upgrade in the billing tab of our control panel. If you don’t have a NodePing account yet, please sign up for a free 15-day trial of our Provider plan at

Twitter Notifications

NodePing is happy to announce our newest notification method – twitter direct messages.  The ability to receive a twitter direct message is a great addition to our current notification system that already includes unlimited email, international SMS, and voice calls.

Twitter notifications are in testing at this point.  They are available on all accounts so please do kick the tires and let us know how things work for you at

You’ll need to follow @NodePing in order to get direct message alerts.  Then add your twitter handle in your contact record and in your check’s notification section and we’ll send you a private and discrete ‘direct message’ (not an embarrassing public tweet) when that check goes down and again when it comes back up.

Let us know in the comments how this new notification type is working for you and what you’d like to see added next – instant message (IM), HTTP POST to url, carrier pigeon, etc?

Now with Unlimited International SMS

Until today, NodePing  offered SMS notifications only to US-based numbers. But do not despair, our friends across the great ponds, we’re happy to announce that we’ve added unlimited international SMS notifications to our server monitoring service. Just add your mobile number to your contact record in plus format (example for UK ‘+445555555555’), and then set it as the notification number in your checks. As always, here at NodePing, it doesn’t cost any extra.  Same great service, same great price – you’ve leveled up!

Globally, mobile networks have a lot of variability and it is possible that some carriers won’t work with our SMS initially. If that’s the case with your carrier please let us know and we’ll do what we can to resolve it.

Give us a digital high-five in the comments if you’re glad to see international SMS added to NodePing!