ASM supports the configuration of webhooks in order to deliver customized, automated messages to predefined endpoints. The information which is delivered to these webhook endpoints can be static or dynamic.
What are Webhooks?
The concept of a Webhook is simple. A Webhook is an HTTP callback: an HTTP POST that occurs when something happens; i.e. a simple event-notification via HTTP POST. This means that Webhooks can deliver alerts using an HTTP POST, sent to any service with a configured URL that supports WebHooks. With no limit on what can be done with the posted information, applications can use WebHooks to perform any desired action.
The flexibility of a webhook allows ASM users to send much more data in an alert than they would be able to do using a non-webhook alert.
| Tip |
|---|
ASM Webhook alerts carry information to your Webhook-enabled service/application target(s) via data placeholders. |
What Are Some ASM Webhook Features?
...
Check Location
Check Description
Check Name
Date & Time of alert
Etc.
ASM Webhook Integrations
The following are links to pages dedicated to integrating Apica ASM to various Webhook-enabled platforms and services.
...
Integrations
...
Links
...
Custom
...
...
The Custom integration allows Alerts can be delivered to any service through a WebHook.
Note: For delivery to work, there needs to exist a receiving WebHook to handle the request.
...
OpsGenie
...
The OpsGenie integration allows Alerts to be delivered to OpsGenie via the Default API Integration.
...
ServiceNow
...
The ServiceNow integration allows Alerts to be delivered to ServiceNow IntegrationHub.
...
Slack (Webhooks Deprecated)
...
The Slack integration allows Alerts to be delivered to Slack channels, however Slack has Deprecated using Webhooks.
...
Splunk
...
.