Commit 7f2b1775 authored by Vitali Tatarintev's avatar Vitali Tatarintev

Add content-type to Generic Alert docs

Since Generic Alert Endpoint expects JSON as a payload
it should have a "Content-Type: application/json"
parent 753eefb0
...@@ -13,11 +13,11 @@ authored by the GitLab Alert Bot. ...@@ -13,11 +13,11 @@ authored by the GitLab Alert Bot.
## Setting up generic alerts ## Setting up generic alerts
To set up the generic alerts integration: To set up the generic alerts integration:
1. Navigate to **Settings > Integrations** in a project. 1. Navigate to **Settings > Integrations** in a project.
1. Click on **Alert endpoint**. 1. Click on **Alert endpoint**.
1. Toggle the **Active** alert setting. The `URL` and `Authorization Key` for the webhook configuration can be found there. 1. Toggle the **Active** alert setting. The `URL` and `Authorization Key` for the webhook configuration can be found there.
## Customizing the payload ## Customizing the payload
...@@ -35,7 +35,11 @@ You can customize the payload by sending the following parameters. All fields ar ...@@ -35,7 +35,11 @@ You can customize the payload by sending the following parameters. All fields ar
Example request: Example request:
```sh ```sh
curl --request POST --data '{"title": "Incident title"}' --header "Authorization: Bearer <autorization_key>" <url> curl --request POST \
--data '{"title": "Incident title"}' \
--header "Authorization: Bearer <autorization_key>" \
--header "Content-Type: application/json" \
<url>
``` ```
The `<autorization_key>` and `<url>` values can be found when [setting up generic alerts](#setting-up-generic-alerts). The `<autorization_key>` and `<url>` values can be found when [setting up generic alerts](#setting-up-generic-alerts).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment