This article describes how to integrate Anodot using webhooks, and includes:
- Creating a Webhook channel
- Alert Webhook formats (for more information about the different alert types and the payload they send to the webhook, see https://docs.anodot.com)
- Defining basic authentication to webhooks
- Defining a webhook channel with Okta authorization
Note: To set the webhook channel as the recipient when creating/editing alerts, see the instructions here.
Creating a Webhook channel
To create a webhook recipient instance from the main Anodot page:
- From the Navigation Panel, click INTEGRATIONS > Channels. The Channels page is displayed.
- In the top right corner, click + New Channel, and select Webhook.
- In the New Webhook Channel dialog, define the following:
- Enter an Anodot Channel Name. Choose a name that easily identifies the webhook.
- Enter a URL. Note that when defining a new URL, the URL must be accessible. A good way to test your webhook is with a webhook testing service. A free alternative we recommend for testing purposes is https://webhook.site.
- Choose a Time Zone. The alert information in the webhook will be provided using this time zone.
- [Optional] Authentication - see the sections below.
- If the Role Based Access (RBAC) is enabled in your account, define the Access Settings:
- Select Everyone if you want all registered Anodot users to have access to the data in this channel. In the Add Members dropdown list, select members already registered in Anodot. You can also add email addresses; use a comma-separated list of email addresses.
- Select Selected Groups if you want to restrict access to the data in this channel to specific groups. In the displayed Who can access dropdown list, select the relevant groups.
- Select the Ungroup metrics in alert checkbox if you want to split the trigger at the metric level, so that each metric can be managed separately (for example, an alert with 50 metrics will be separated into 50 separate webhooks). This is especially relevant when different users in your organization are responsible for different regions, departments and so on.
- Click Test Connection to test the channel.
- Click Create Channel.
Note: To ensure the alerts are distributed correctly, make sure your Allowlist includes Anodot server IP addresses. See Allowlist Anodot Servers.
Defining basic authentication to webhooks
[Optional] For additional security, click Authentication. You can choose between basic authentication and Okta based authentication. To use basic authentication, enter the User name and Password.
Defining a Webhook Channel with Okta Authorization
- Access your Okta Admin Console.
- Go to Applications > Applications.
- Click Create app Integration.
- Select API Services as the Sign-in Method.
- Click Next, and then do the following:
- Set a name (for example Anodot Channels) and click Save.
- Click Edit.
- Choose private/public key links.
- Insert the Anodot link:
When defining the webhook channel in Anodot, as described in the section above, you'll need to provide the following:
- Issuer URL: Copy the Issuer URL (you can take it from Security > API > Authorization Servers) of the Authentication server you select. Anodot will take the okta domain, and Authorization Servers from the Issuer URL.
- Client ID which can be taken from the General tab of the app integration.
- Scope Name: Click on the selected Authorization server, and go to Scopes. Select the scope you want to use, this is the Scope Name.