[BUG]

[tomvannostrand]

Describe the bug

Trying to use a Google Webhook for a notification fails. Using other webhooks like Discord and https://webhook.site/ for example work fine.

To Reproduce
Steps to reproduce the behavior:

1. Create a google chat webhook. Copy the link.
2. In the OpenSearch GUI, Go to 'Notifications'
3. Click on 'Channels'
4. Add a notification and paste in your webhook
5. Click test
6. See error

Expected behavior
A notification pops up in google chat

OpenSearch Version
2.9, 2.11

Dashboards Version
2.9, 2.11

Plugins

None

Error message

[status_exception] {"event_status_list": [{"config_id":"N7QfGosBxj32RX8UNdMY","config_type":"webhook","config_name":"google webhooks are broken but heres mine","email_recipient_status":[],"delivery_status":{"status_code":"500","status_text":"Failed to send webhook message Failed: {\n "error": {\n "code": 400,\n "message": "Invalid JSON payload received. Unexpected token.\nTest message content\n^",\n "status": "INVALID_ARGUMENT"\n }\n}\n"}}]}

If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

• OS: N/A
• Browser and version: Chrome, but this is a UI bug not a browser bug.

Additional context

I'm using a webhook generated in google chat. For instance my host was: chat.googleapis.com

I've tried fiddling with manual webhook settings to no avail. It seems that whatever format OIpenSearch is sending to google, Google doesn't like it as it doesn't somehow conform to their formatting.
Because OpenSearch can send to other webhooks, just not google's but other things can send to google webhooks just fine, I believe the problem should be fixed within OpenSearch. Perhaps all webhook notifications could be modified to some lowest common denominator formatting, or perhaps in the manual settings, there could be a "and fix formatting to conform to google" button, or at least a way to manually modify whatever is breaking.

[SuZhou-Joe]

This looks more like the payload format check between notification and google chat. Transfer to notification repo.

[zhichao-aws]

Hi @tomvannostrand , can you give a sample curl request to use the google webhook? For example: curl -H 'Content-Type: application/json' -d '{"text": "Hello World"}' . I want to make sure the json structure is consistent with our custom webhook.

[Hailong-am]

@tomvannostrand you can choose slack as notification type and input google webhook endpoint, they share same json schema.

[tomvannostrand]

Sure enough! Picking "Slack" instead of "Custom Webhook" allows me to use a google webhook.
Suggest renaming these to "Standard Webhook" and "Custom webhook that you can't customize enough to work with google because customization options are too limited"

[tomvannostrand]

Thank you @Hailong-am and @zhichao-aws. I've closed this but the problem remains that "Slack" should be renamed.