Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Apica Alerts can be delivered to any service through a Custom Webhook Integration.
...
Step | Screenshot | ||
---|---|---|---|
Create a Custom Service Target by clicking the WebHook button | |||
A blank target is created | |||
Select the Service | |||
The Service section allows you to select the service type that we are going to send an alert to.
|
| ||
The following steps refer to the following Custom Service dialog | |||
Set a Target NameThe target name identifies the target in Synthetic Monitoring.
Required! This field is required in Apica Synthetic. The exact contents of the field may depend on the requirements of your service. | General - Service NameIn the Service Name section, you can provide the ID or name of the service that should receive the alerts. | ||
Add Target Details | |||
Set AuthenticationSet your Authentication, including | Global AuthenticationIn the Global Authentication section, you can choose and configure the type of authentication to use for alert delivery. | ||
Request HeadersDefine theHTTP Header Type and value pairs to attach to different request types. | |||
Request TypesSend the Service if the request is a Trigger, Resolution, Authentication, or a refreshed access token | T (Trigger): Trigger an alert. R (Resolve): Resolve an alert. A (Authenticate): Authenticate using the access token. F (Refresh): Request with refresh token for a new access token. | ||
Header ContentMultiple headers can be added by clicking the Add button | Name: The name of the header. Value: The value of the header. | ||
Response ParametersExample: A RESTful service has the Multiple parameters can be added by clicking the Add button | The Response Parameters section lets you define parameters in responses to store for use in future requests. XPath: The XPath for the parameter in the response. Example: Placeholder: A Webhook Placeholder to be replaced with the actual value. Example: Is Auth?: Indicates (1) if the parameter is used for authentication and (2) that the parameter has an expiration time. Any time the Alerter fails to authenticate, it will clean up all values for this parameter. | ||
Trigger Sequence | A procedure page on entering the Trigger Request Sequence configures the steps to begin a Webhook alert handling instance. | ||
Resolve Sequence | A procedure page on entering the Trigger Resolve Sequence configures the steps to begin a Webhook alert handling instance when the alert has been resolved. i.e. to notify when the situation has been corrected or the event has ended. | ||
(Done) Add Custom Webhook Target | When you are happy with all the settings, you can create the target. Click the Add Custom WebHook Target button |
...