VictorOps + Zebrium Integration Benefits
- Automatically adds root cause to a VictorOps incident triggered by any existing monitoring, APM, log manager, help desk tools, etc.
- Each incident is augmented with a clear set of events and charts showing root cause and symptoms.
- This means faster MTTR and less hunting for root cause.
How it Works
- Any existing monitoring, APM, logger, help desk tool raises an alarm.
- Through an existing integration with VictorOps, an incident is created.
- At that same instant, VictorOps automatically calls an outbound webhook to Zebrium with all the incident details.
- Zebrium correlates those incident details with its Autonomous Incident Detection and Root Cause by looking across logs and metrics.
- The VictorOps incident is updated with Zebrium Incident details and likely root cause via the VictorOps API.
- If you need to drill down further to logs or metrics, it’s just one click from your VictorOps Incident.
Requirements
- VictorOps user must have permissions to create API Keys and Outgoing Webhooks
Support
If you need help with this integration, please contact Zebrium by email to support@zebrium.com
Integration Walkthrough
In VictorOps (part 1 of 2)
Configuring API Access for Zebrium
- From the Integrations tab, select API.
- Click the + New Key button.
- Enter a description (e.g. Zebrium Incident Detection).
- Click the Create Key button.
- Copy the API ID and the API KEY and save for later use when configuring Zebrium.
In Zebrium (part 1 of 1)
Configuring a Webhook for VictorOps
- From the User menu area, click on the Settings Menu.
- Click the Inbound Integrations menu item.
- Click the Create Inbound Integration button, select VictorOps as the Inbound Integration Type and click Create.
- Enter the VictorOps API ID that was copied in step 6 above when Configuring API Access for Zebrium
- Enter the VictorOps API Key that was copied in step 6 above when Configuring API Access for Zebrium
- Click the Create button.
- Copy the Incoming Webhook URL and save for later use when configuring the VictorOps Outgoing Webhook.
In VictorOps (part 2 of 2)
Adding the Zebrium Webhook to VictorOps
- From the Integrations menu, select Outgoing Webhooks.
- Click the + Add Webhook button.
- In the Event drop-down menu, select Incident-Triggered
- In the Method drop-down menu, select POST
- In the Content-Type drop-down menu, select application/json
- Do not Add Custom Header
- In the To text box, enter the Incoming Webhook URL that was copied in step 8 above when Configuring a Webhook for VictorOps.
-
In the Payload text box, enter the following:
{ "ze_entity_type" : "${{INCIDENT.ENTITY_TYPE}}", "ze_ack" : "${{STATE.ACK_MSG}}", "ze_user" : "${{STATE.ACK_USER}}", "ze_timestamp" : "${{STATE.ACK_TIMESTAMP}}", "ze_alert_ct" : "${{STATE.ALERT_COUNT}}", "ze_current_alert_phase" : "${{STATE.CURRENT_ALERT_PHASE}}", "ze_current_state" : "${{STATE.CURRENT_STATE}}", "ze_entity_id" : "${{STATE.ENTITY_ID}}", "ze_host" : "${{STATE.HOST}}", "ze_incident_name" : "${{STATE.INCIDENT_NAME}}", "ze_incident_timestamp" : "${{STATE.INCIDENT_TIMESTAMP}}", "ze_last_timestamp" : "${{STATE.LAST_TIMESTAMP}}", "ze_monitor_type" : "${{STATE.MONITOR_TYPE}}", "ze_service" : "${{STATE.SERVICE}}" }
- Enter a description (e.g. Zebrium Incident Detection).
- Click the Save button.
How to Uninstall
In VictorOps
Disable API Access
- From the Integrations tab, select API.
- Click X on the desired API Key.
- Click the Delete Key button after confirming you wish to proceed.
Delete Outgoing Webhook
- From the Integrations menu, select Outgoing Webhooks.
- On the desired Outgoing Webhook, pull down the menu and select Delete
- Click the Delete button after confirming you wish to proceed.
In Zebrium
Disable Webhook for VictorOps
- From the User drop-down menu, select Settings.
- Click the VictorOps tab.
- Hover over the webhook you wish to remove and click the Red X.
- Click the Continue button after confirming you wish to proceed.