Site24x7 Logo

Site24x7 Integration Guide

Site24x7 offers unified cloud monitoring for DevOps and IT operations. It allows companies to keep track of their entire online system from a single console. With TaskCall's Site24x7 integration, incidents identified by Site24x7 are brought to the forefront so they can be addressed by on-call responders in the fastest possible time.

Pointers

  • The integration is between a TaskCall service and Site24x7.
  • Incidents will automatically resolve in TaskCall when Site24x7 issues resolve.
  • This integration only allows alerts to be received in TaskCall from Site24x7.

In TaskCall

  1. Go to Configurations > Integrations and click New Integration.
  2. Select the Site24x7 integration.
  3. Give the integration a name and configure how incidents will be created. Only the Default Service field is required. The rest are optional.
  4. Incidents (Optional)
    1. TaskCall automatically maps incoming payloads with internal attributes to create incidents. However, this can be customized in the Incidents tab. Constant values can be included alongside placeholders to dictate which attributes should map to the Incident Title, Description, Tags, Snapshots and Vendor URL. To insert a placeholder use double curly braces.

      Incoming Webhook Incident Tab

      For example, if you enter {{ alert.title }} in the Incident Title field, TaskCall will look for an attribute called "title" nested inside another attribute called "alert" in the incoming payload. If the nested attribute exists, its corresponding value will be pulled from the payload and inserted. If the nested attribute does not resolve successfully, TaskCall will fall back to the default mapping.

      If you are unsure, please leave the fields empty. TaskCall will use the default mapping to create the incident for you.
    2. Select the Urgency level the incident should be created at.
    3. Select the option to Group similar alerts together if you would like follow up triggers from the same alert source to be grouped into the same incident. If you leave this option unchecked, then a new incident will be created for every trigger. (This behavior is specific to new triggers; not updates to an alert.)
    4. Click Next to move on to the Services tab.
  5. Services (Required)
    1. Select the Default Service incidents should be sent to. To route incidents to different services instead, set Map With Attribute to the attribute to route by using a placeholder. Then, map each value it can take to the service that should receive it.

      For example, to route by a region attribute sent in the payload, set Map With Attribute to {{ region }}, then map US to one service and EU to another, and so on.

      Incoming Webhook Services Tab
    2. Click Next to move on to the Authorization tab.
  6. Authorization (Optional)
    1. The Authorization tab allows a Bearer Token and an IP Allowlist be added if you would like to restrict who is able to send alerts to this integration. If you are unsure, this can be skipped.
  7. Once done, click Save.
  8. Copy the Integration Url that is issued for the integration. This will be used to set up the notification in Site24x7.

In Site24x7

  1. Go to Admin > Third-Party Integrations > Webhooks.

    Site24x7 Integration Step 1

  2. Now fill up the webhook integration form:
    • Give the integration a name (as a suggestion, you can call it TaskCall to help you identify it easily).
    • Paste the integration URL you copied over from TaskCall.
    • Select POST as the HTTP method, and ennsure to checkmark the boxes labelled Post as JSON and Send Incident Parameters.
    • Make sure to select the correct monitors in the Integration Level
    • .
    • Select under what statuses of the monitor incidents should trigger.


    Site24x7 Integration Step 2

  3. Click Save.
Done! You have successfully integrated with Site24x7. Incidents will now be created on TaskCall for alerts that are triggered from Site24x7.
On this page