IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Torq connector and actionedit
The Torq connector uses a Torq webhook to trigger workflows with Kibana actions.
Create connectors in Kibanaedit
You can create connectors in Stack Management > Connectors or as needed when you’re creating a rule. For example:
Connector configurationedit
Torq connectors have the following configuration properties:
- Name
- The name of the connector. The name is used to identify a connector in the Stack Management UI connector listing, and in the connector list when configuring an action.
- Torq endpoint URL
- Endpoint URL (webhook) of the Elastic Security integration you created in Torq.
- Torq authentication header secret
- Secret of the webhook authentication header.
Test connectorsedit
You can test connectors with the run connector API or as you’re creating or editing the connector in Kibana. For example:
Torq actions have the following configuration properties.
- Body
- JSON payload to send to Torq.