1. Home
  2. Integrations
  3. Dotcom-Monitor Integration Guide – VictorOps

Dotcom-Monitor Integration Guide – VictorOps

 Dotcom-Monitor provides a software as a service that simulates real-user internet connections and transactions while reducing down time and optimizing performance and user experience.

The VictorOps integration with Dotcom-Monitor creates an Incident in the VictorOps Timeline whenever a Dotcom-Monitor alert is triggered. The following is a quick walkthrough on how to set up the integration.


  1. From the Dotcom-Monitor UI select Configure ==> Alerts ==> Templates ==> Add New Templatesdotcom1
  2. Enter the following information for the Error Source, Test Source and Uptime Source fields:
    Name CURL
    Email Subject N/A
    Email Reply-tp N/A
    Type Text
    Error Source {“message_type”:”critical”,”monitoring_tool”:”Dotcom-Monitor”,”state_message”:”Error occurred during the device monitoring at <%Monitor_DateTime%> Monitoring location:<%Location%>”,”entity_id”:”<%Site_Name%>”}
    Test Source {“message_type”:”critical”,”monitoring_tool”:”Dotcom-Monitor”,”state_message”:”Test message”,”entity_id”:”Test message”}
    Uptime Source {“message_type”:”recovery”,”monitoring_tool”:”Dotcom-Monitor”,”state_message”:”Device <%Site_Name%> detected to be back online at <%Monitor_DateTime%> from monitoring location: <%Location%>”,”entity_id”:”<%Site_Name%>”}
  3. Select Add New Monitoring Device on the device list page. This can be found in the Devices menu.dotcom2
  4. In VictorOps, select Settings >> Alert Behavior >> Integrations >> Dotcom-Monitor.

    If the integration has not yet been enabled, click the “Enable Integration” button to generate your endpoint URL as seen below.  Be sure to replace the “$routing_key” section with the actual routing key you intend to use. (To view or configure route keys in VictorOps, click Alert Beahvior >> Route Keys)

    • YOUR_REST_ENDPOINT_API_KEY_HERE with your VictorOps key (see step 4)
    • YOUR_ROUTING_KEY_HERE with the appropriate VictorOps Routing Key so that incidents are routed to the correct team.
    • “<Template ID>” with the ID of a template which can be seen in URL field of your browser when editing a template.On a device edit screen put the following in Custom Script file field:Url_PostExecutor.cs "https://alert.victorops.com/integrations/generic/20131114/alert/YOUR_REST_ENDPOINT_API_KEY_HERE/YOUR_ROUTING_KEY_HERE" "<Template ID>"Make sure to replace:


  5. Save your device and you’re done!
Updated on March 10, 2017

Was this article helpful?

Related Articles