StatusPal
StatusPal.ioBlog
Documentation
Documentation
  • Introduction
  • Get Started
    • Key concepts
    • Step 1 - Configure services
    • Step 2 - Add your team
    • Step 3 - Personalize design
    • Step 4 - Enable notifications
    • Step 5 - Report an incident
  • Next Steps
  • FAQ
  • 1-Click Import
    • Atlassian Statuspage Importer
    • Status.io Importer (beta)
  • Platform
    • Services/components
      • Dependencies
    • Subscriptions & Notifications
      • Subscriptions
      • Notifications
      • Auto-maintenance notifications
      • Subscription Groups
      • Import email subscribers
      • Auto-subscribe to private status page
      • Custom email templates
        • Template examples
    • Incidents & Maintenance
      • Reporting an Incident
      • The Uptime Calendar Page
      • Custom Incident Types
      • Exporting your incidents
    • Information Notices
    • Private Status Page
      • Adding people to your status page
      • Access Groups/Audience Specific
    • Team Members
    • Status Page Settings & Design
      • Custom Domain
      • Advanced Settings
      • Design Customization
        • Design recipes
    • Multi-Language
    • Status Badge & Banner Widget
    • Integrations
      • Terraform
      • Datadog Metrics
      • Zoom Notifications
      • Google Analytics
      • Google Calendar
      • SendGrid Email Notifications
      • PagerDuty + Statuspal status page
      • Configure SSO for your status page with Okta
      • Configure SSO for your status page with Auth0
      • Configure your Mailgun Integration
      • Configure SMS Notifications (Twilio Integration)
      • Zabbix
      • Pingdom
      • Checkly
      • New Relic
      • Datadog
      • BetterUptime
  • Monitoring & automation
    • Out-of-the-box monitoring
    • Incident automation
    • Recurring maintenance
  • Security
    • Single Sign-On
      • Save your Recovery Codes
      • Configure Role provisioning from SAML attributes
      • Configure role provisioning for Okta
    • API Keys
Powered by GitBook
On this page
  • Create your Webhook Integration in StatusPal
  • Create your Webhook Integration in New Relic
  • Create your Synthetic Monitor in New Relic
  1. Platform
  2. Integrations

New Relic

This guide outlines the steps to integrate StatusPal's monitoring service with New Relic's synthetic checks. This integration allows you to receive alerts in StatusPal via webhook

PreviousChecklyNextDatadog

Last updated 2 months ago

To automate the reporting and closing of incidents on your status page based on the status reported by New Relic synthetic checks, follow these steps.

Create your Webhook Integration in StatusPal

First, you need to create an endpoint URL within StatusPal. This URL will act as the bridge between New Relic and StatusPal, receiving notifications from New Relic about uptime check results via webhook.

  • Navigate to Services: On your Status Page, create a new service or edit an existing service.

  • Add Webhook: On Monitoring and incident automation section, check on Webhook and select NewRelic.

  • Finish and Save: Create or update the service, then copy the endpoint URL that will be created for you.

Create your Webhook Integration in New Relic

Next, you need to create a webhook and workflow within New Relic.

  • Navigate to Alerts: On the New Relic navigation bar, click on Alerts.

  • Add a Destination: On the Alerts' navigation bar, click on Destinations and them on Webhook.

  • Add Webhook: In the new webhook configuration, you'll need to add the endpoint URL provided by StatusPal. This URL is specific to your StatusPal service configuration and is essential for the integration to work correctly. Paste this URL into the appropriate field.

  • Create a Workflow: On the Alert's navigation bar, click on Workflows and then click on Add a workflow.

  • Configure Workflow: On the configuration of the workflow, on the Filter data section, select on Priority the option CRITICAL. Please note that if you have more than one ping monitor, you need to set a tag in order to link it to the workflow. Then on the Add a channel section click on Webhook to open the notification message. Furthermore on Destination option, select the webhook you created for StatusPal.

  • Payload configuration: On the notification message, you can configure the payload that will be send to StatusPal. We strongly suggest that you keep the default template. However, if you prefer to configure it because you will use this workflow somewhere else, you must keep 2 properties on the json object:

{
  "priority": {{ json priority }},
  "state": {{ jason state }},
  Rest or your properties...
}

Create your Synthetic Monitor in New Relic

Next, you need to configure your synthetic monitor in New Relic and link it to the webhook you just created.

  • Navigate to Synthetics: On the New Relic navigation bar, click on Synthetic Monitoring.

  • Create Monitor: Click on Create monitor and create a new monitor for the synthetic you want to track using the Availability - Ping template. Configure the monitor according to your needs (e.g., check frequency, target URL). Please note that if you have more than one ping monitor, you need to set a tag in order to link it to the workflow.

That's it! Once you have completed these steps, New Relic will send notifications about your uptime checks to StatusPal, allowing you to monitor and manage your service availability from a centralized platform.