1. Home
  2. Integrations
  3. Site24x7 Integration Guide – VictorOps

Site24x7 Integration Guide – VictorOps

Requirements

Versions Supported: N/A (SaaS)

VictorOps Version Required: Enterprise

Site 24×7 allows you to monitor websites remotely and receive alerts if your website becomes unavailable. This integration uses a Site 24×7 Third Party Integration and the VictorOps Site24x7 Integration endpoint.

In VictorOps

Retrieve your Site 24×7 endpoint URL. To do, so go to Integrations >> Site 24/7

 

Select the Site 24×7 icon, enable the integration, then copy the URL to your clipboard.

Please remember to replace the $routing_key with an actual VictorOps routing key, as defined HERE.

In Site 24×7

From the main web portal select Admin then Third Party Integration then Actions then Webhooks.

On the webhook configuration screen, fill in the values as follows and then click Save:

Field Name
Value
Integration name victorops
Hook URL <url_from_victorops_account>
HTTP Method POST
Post as JSON TRUE
Send Incident Parameters TRUE
Send Custom Parameteres TRUE
Custom Parameters {
   "message_type": "critical",
   "monitoring_tool": "Site24x7",
   "state_message": "$INCIDENT_REASON",
   "entity_display_name": "$INCIDENT_REASON"
}
Integration level All Monitors

Auto Resolve Configuration

A rules engine rule is needed in order for site 24×7 incidents to resolve in VictorOps when the monitor status is “UP”. The rule will be configured to state:

When status matches *UP* using wildcard, set message_type to RECOVERY.

Also, the entity_id will need to be added in site 24×7 custom parameters. VictorOps uses the entity_id to uniquely identify incidents, so if incidents have the same entity_id, they will aggregate. This also means that if an incident enters VictorOps, another alert with the same entity_id and a message_type RECOVERY will resolve the incident. The entity_id configuration within the custom parameters depends on your use case. Reach out to support if you need assistance!

Notify VictorOps only on Select Monitors

Note that there are varying ways to leverage a third party integration to apply more granular alerting settings. To only notify VictorOps on select monitors, change the Integration from All Monitors to Monitors.

For even further customization of how and under what monitor conditions VictorOps should be notified, Notification Profiles can further specify waiting rooms, alert frequency and number of failed results before firing a webhook.

Updated on June 18, 2020

Was this article helpful?

Related Articles