> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/hyperping.md).

# Hyperping

Steps to configure Hyperping integration for incident management, using Squadcast

[<mark style="color:blue;">Hyperping</mark>](https://hyperping.io/) is an uptime monitoring platform for websites, APIs, and public status pages.

Route detailed alerts from Hyperping to the right users in Squadcast.

### How to integrate Hyperping with Squadcast

### In Squadcast: Using Hyperping as an Alert Source

1. Navigate to **Services** -> **Service Overview** -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click **Add**.

![](https://1574591692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8TaWz01jmUJl58p4ZVel%2Fuploads%2Fgit-blob-4fbd74e7ca0b30173c47a1d58ed6a0804a0465aa%2FAlert_Sources.png?alt=media\&token=aaca6610-9d18-4dd4-9cf5-320042f326f1)

1. Select **Hyperping**. Copy the displayed **Webhook URL** to [configure](#in-hyperping-set-up-a-webhook-for-squadcast) it within **Hyperping.** Finish by clicking **Add Alert Source** -> **Done**.

![](https://1574591692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8TaWz01jmUJl58p4ZVel%2Fuploads%2Fgit-blob-a47b9002d9ff00c07c65eb5dda22cc6c84d01606%2FHyperping.png?alt=media\&token=a7d685a9-ae76-45da-9336-13d80c3991aa)

{% hint style="warning" %}
**Important:**

When an alert source turns Active, it’ll show up under Configured Alert Sources, you can either generate a test alert from the integration or wait for a real-time alert to be generated by the Alert Source. An Alert Source is active if there is a recorded incident via that Alert Source for the Service.
{% endhint %}

### In Hyperping: Set up a Webhook for Squadcast

1. Click on **Project** and navigate to **Project settings**
2. Paste the previously copied Squadcast **Webhook URL** in the **URL** field under the **Webhook** section

![](https://1574591692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8TaWz01jmUJl58p4ZVel%2Fuploads%2Fgit-blob-ff35293d9cd387df5aa5b7e38963c7225d726c11%2Fhyperping_2%202.png?alt=media)

{% hint style="info" %}
**Information**:

You can test the newly configured webhook by clicking on `Down test`. This will trigger a test alert in Squadcast. Clicking on `Up test` may or may not send out the *correspoding* resolve signal to Squadcast for auto-resolution of the newly triggered incident.

However, if you see that a test alert is triggered in Squadcast when you click on `Down test`, you can be rest assured that the integration will work as expected.
{% endhint %}

{% hint style="info" %}
**Note**:

You can configure webhooks in Hyperping across different Projects as well.

That is it, you are now good to go!

In Hyperping, whenever an event is generated with `down: true`, an incident will be created for it in Squadcast. When an event is generated with `down: false`, the corresponding incident will automatically get resolved in Squadcast as well.
{% endhint %}

{% hint style="info" %}
**Helpful Links to Hyperping's Documentation**:

You can find more information on setting Webhooks up [here](https://hyperping.io/docs/integrations/webhooks).
{% endhint %}

*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*