Webhooks in Riverbed IQ Ops
Riverbed IQ Ops supports the execution of runbooks
An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook. by webhooks sent by other applications An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies.. This is useful for creating incidents A collection of one or more related triggers. Relationships that cause triggers to be combined into incidents include application, location, operating system, or a trigger by itself. in Riverbed IQ Ops based on alerts raised in other applications. In such cases, the other application sends a webhook to Riverbed IQ Ops, which handles the webhook as a Webhook trigger A set of one or more indicators that have been correlated based on certain relationships, such as time, metric type, application affected, location, or network device., 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 Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. 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 Ops. 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:
