Webhooks in Riverbed IQ
Riverbed IQ supports the execution of runbooks by webhooks sent by other applications. This is useful for creating incidents in Riverbed IQ based on alerts raised in other applications. In such cases, the other application sends a webhook to Riverbed IQ, which handles the webhook as a Webhook trigger, and executes the mapped runbook using the data acquired from the webhook.
The runbook can access these data from the trigger:
-
HTTP Request URL — An object containing path parameters in the inbound request.
-
HTTP Request Query Parameters — An object containing query parameters in the inbound request.
-
HTTP Request Headers — An object containing headers in the inbound request.
-
HTTP Request Body — A complex data object that defines the body structure of the inbound request.
When creating a runbook for use with a webhook, the first node in the runbook is the Webhook trigger, followed next by a Transform node, an HTTP Request node, or a Set Simple Variable node. Use a Transform node if you need to transform the webhook's JSON content into a format that can be used by Riverbed IQ. An HTTP Request node, whether it follows the Webhook trigger node immediately, or follows a Transform node, can acquire data from the webhook for use downstream in the runbook sequence.
For example:
