In the platform menu, under the “Teams” option,we can configure communication channels where you want to receive our notifications.
Each team can have different notification channels and we support notifications via webhook.
To configure notifications, select “Teams”. To create a new team, click on the “New” button located at the upper right corner of the screen and follow the setup process.
For registered teams, navigate to the desired team and click on the “Notifications” tab in the top toolbar. Check the box next to the option with the webhook icon, then enter the URL.
Next to the Webhook option, there is a field to enter the url and then the “TEST” button that sends a test to the configured url.
When the webhook notification test is performed, the POST sent to the webhook is done from the browser itself. Browsers use CORS to avoid security problems when a website makes requests to other domains.
Due to the CORS policy, the browser first sends an OPTIONS request to the webhook before sending the POST request. This is to verify if the server responds with headers that comply with the CORS policy. Therefore, for the test to succeed, your webhook must have CORS enabled
Notification via webhook sends a POST request to the specified address, with a payload in the following format:
{
"type": "hit/fail",
"title": "Site",
"description": "Could not get IP address for domain https://site.com, lookup site.com on 10.40.0.2:53: no such host",
"status": "alarmed",
"uid": "",
"failure_happened_at": "2024-02-29T13:11:16.398102Z",
"incident_resolved_at": "2024-02-29T13:11:17.311918Z",
"status_page_id": 0,
"status_page_url": "",
"org_uid": "a6bf25a0-0c35-49a9-817f-1bc1d1b6cb89",
"addon_id": 0,
"addon_name": "",
"application_id": 158,
"application_name": "Site",
"product_id": 1,
"product_name": "",
"affectedByIssue": null,
"addon_pool": null,
"incident_id": 1,
"incident_type": "hit/fail",
"incident_data": null,
"severity": "not-classified"
}