🆕 Webhook Overview
...
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.
What this means to the Apica Monitoring User:
In ASM, when you want to send an alert for any of your checks, feel free to use Webhooks to do so.
...
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 Some ASM Webhook Features?
Apica integrates with 3rd-Party Alerting services, allowing companies using ASM to have alerts sent to the receiving management system of their choice.
...
Check Location
Check Description
Check Name
Date & Time of alert
Etc.
Why use Webhooks? Business Value
Correlating is more manageable when collecting several systems' incident alerts in a single system.
So incident management systems can better track and manage the lifecycle of monitoring incidents using escalation and on-call schedules.
This in turn can help improve vital KPI's such as Time To Acknowledge and Time To Resolve.
Who can use Webhooks? Target Audience
Webhooks are useful for the following groups:
IT Operations departments wanting to manage alerts in an external system.
Digital Experience / Business Units / Business Owners to be kept up to date on incidents or performance issues.
DevOps teams that own the operation of a service and need monitoring of alerts.
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 | The Splunk integration allows Alerts to be delivered as messages to a Splunk instance. |
Configuring Webhooks in ASM
When defining alert recipients, you can have the message delivered via various target services. To begin, navigate to the ManageAlerts/Alerts endpoint by clicking on Manage > Alerts from the top toolbar in ASM:
...
Then, click on the “Recipients” button on the top right of the screen:
...
Now you can targets, which are Users or Groups of Users who can receive alerts at different endpoints.
Targets
For each User or Group Recipient, you add delivery Targets which define the method of delivery.
User
You can select to add PagerDuty, Email, a WebHook integration, or SMS (text message) as targets.
...
Groups
When you have defined targets for individual users, you can add them to Groups:
...