From 851ed11fb12af376b14d8d8db1f0878415d94d1b Mon Sep 17 00:00:00 2001 From: P Precious Date: Tue, 12 Aug 2025 23:13:39 +0530 Subject: [PATCH] update docs for setting up the alert. (#22919) --- .../v1.9.x/how-to-guides/admin-guide/alerts.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/openmetadata-docs/content/v1.9.x/how-to-guides/admin-guide/alerts.md b/openmetadata-docs/content/v1.9.x/how-to-guides/admin-guide/alerts.md index acf4fe4d7af..79c883af567 100644 --- a/openmetadata-docs/content/v1.9.x/how-to-guides/admin-guide/alerts.md +++ b/openmetadata-docs/content/v1.9.x/how-to-guides/admin-guide/alerts.md @@ -161,4 +161,16 @@ For MS Teams configuration you will need to get the endpoint URL of the channel To set up a webhook you can simply use the endpoint URL where you want your alert to be sent. Additionally, you can configure the following parameters: - **Batch Size**: Size of the batch that will be sent to the endpoint. - **Connection Timeout**: Timeout for the connection. -- **Secret Key**: Secret key can be used to secure the webhook connection. \ No newline at end of file +- **Secret Key**: Secret key can be used to secure the webhook connection. + +## Advanced Configuration + +For these destinations type (Webhook, Slack, Microsoft Teams, Google Chat), OpenMetadata provides **Advanced Configuration** options that allow you to customize the request details sent to the destination endpoint. + +1. **Headers** : Add custom HTTP headers to be included in the webhook request. + +2. **Query Params** : Define additional query parameters to append to the webhook URL. + +3. **HTTP Method** : Choose the HTTP method to be used when sending data: + 1. **POST** (default) + 2. **PUT** \ No newline at end of file