ERROR [pool-xxxx-thread-x] com.vmware.vcops.platform.notification.webhook.WebhookSender.call - Failed to send POST; status code: 404
ERROR [ServerConnection on port 10000 Thread xxx] com.vmware.vcops.alertplugins.webhook.WebhookPlugin.test - Expected POST HTTP status code 200 but received 404
ERROR [pool-xx-thread-x] com.vmware.vcops.alertplugins.webhook.WebhookPlugin.createWebhookMessage - Invalid JSON payload:
{"startDate":"xxx xxx xx xx:xx:xx UTC xxxx","updateDate":"xxx xxx xx xx:xx:xx UTC xxxx","cancelDate":"xxx xxx xx xx:xx:xx UTC xxxx","resourceId":xxxxx","adapterKind":"VMWARE","resourceKind":"VirtualMachine","resourceName":"xxxxxx__VM_OEL7-pivotal-tomcat-activeMq","Health":"1.0","Risk":"1.0","Efficiency":"1.0","impact":"health","criticality":"info","alertName":"__TEST_ALERT","type":"Application","subType":"Performance","alertId":"xxxx","status":"Canceled","recommendations":"a | [xxxxx] <div>__
1. Assign correct FQDNs to all Manager nodes and verify the DNS configuration is correct for successful lookup of all Manager nodes' FQDNs.
2. Alternatively, deactivate the use of FQDNs by invoking the NSX API PUT /api/v1/configs/management with publish_fqdns set to false in the request body.\\\ [xxxxx] After that calls from Transport nodes and from Federation to Manager nodes in this cluster will use only IP addresses.</div>","alertURL":"https://xxx.xxx.xxx.xxx/vcf-operations/ui/inventory;mode=hierarchy;resourceId=xxxx;tab=alerts-and-symptoms;subTab=alerts;entityId=xxxxxxx"}
JSON
payloads, causing errors during the webhook POST
requests. As a result, the webhook plugin fails with a 404
status code, and no alerts or notifications are generated.Manually removing any special characters from the notification template payload. This can temporarily resolve the issue and allow the webhook to function correctly.