Webhook payload notification failures due to inline Symptoms variable formatting

Products

• VCF Operations

Issue/Introduction

Outbound webhooks in VCF Operations fail to deliver when integrating with third-party HTTP endpoints like ServiceNow or Slack. The delivery error occurs when the ${SYMPTOMS} variable is embedded directly inside a quoted string field.

Symptoms:

• Webhook delivery fails or generates parsing errors.
• Error messages appear when the ${SYMPTOMS} variable is placed inside a description string.

Environment

VCF Operations 9.x

Cause

The webhook payload schema evaluates ${SYMPTOMS} as a structured, nested JSON object (containing symptoms and conditions). When this object is embedded inline within a quoted text string, it invalidates the JSON payload structure, causing processing failures at the receiving endpoint.

Resolution

Move the ${SYMPTOMS} variable out of any inline string values and assign it to its own dedicated JSON key within the payload template.

1. Navigate to Administration > Configuration > Payload configuration in the VCF Operations user interface.
2. Edit the target outbound webhook payload template.
3. Reformat the payload so ${SYMPTOMS} is not enclosed in quotes inline with other text.
   • Incorrect Payload Example (Inline string formatting):

     {    "description": "ABS:VMware CRITICAL Alert on ${RESOURCE_NAME} on ${SYMPTOMS}"}

   • Correct Payload Example (Dedicated JSON key formatting):

     {
       "description": "VMware CRITICAL Alert on ${RESOURCE_NAME}",
       "symptoms": "${SYMPTOMS}"
     }

4. Save the payload template and trigger a test notification to verify delivery.