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.

pagerduty

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.

Sendgrid’s outage impacted our notification systems

Our notification systems use Sendgrid for email delivery. Overall, Sendgrid has been very reliable and a solid service provider. Today Sendgrid had a fairly significant outage, and that has impacted the timely delivery of some of our email notifications. Obviously for a service like ours this is a big deal.

We are in the process of reviewing our notifications infrastructure to see how our failover systems can be improved to make sure our notifications always get out in a timely fashion. Our apologies to our users who were impacted by this problem.

If you have any questions about this issue, please feel free to email us at support@nodeping.com.

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 NodePing.com.