Skip to main content
NetApp Knowledge Base

Clicking Test Webhook on a DII notification webhook returns HTTP 400 Bad Request

  1. Last updated
  2. Save as PDF
Views:
3
Visibility:
Public
Votes:
0
Category:
data-infrastructure-insights
Specialty:
OM
Last Updated:

Applies to

  • Data Infrastructure Insights (DII)

Issue

  • Clicking Test Webhook on a DII notification webhook returns HTTP 400 Bad Request.
  • The error appears even when the webhook configuration looks correct or live alert delivery works.
  • Common with PagerDuty, Slack, Microsoft Teams, and other JSON webhook integrations.

Cause

  • The DII Test Webhook feature sends the message body exactly as written in the editor.
  • Test Webhook does not substitute default alert parameters (for example %%alertId%%, %%severity%%, %%triggeredOn%%) or custom secrets (for example %%routingKey%%).
  • Third-party endpoints validate required fields and reject placeholder values, which results in HTTP 400.

Solution

  1. Do not use Test Webhook as the sole validation method for integrations that require substituted values.
  2. To test manually, temporarily replace placeholders in the message body with valid literal values (valid PagerDuty Integration Key, valid severity such as warning, non-empty source), run Test Webhook, then restore placeholders before saving.
  3. Validate production behavior by triggering a real monitor alert and reviewing the Status and Last Reported columns on Admin > Notifications > Webhooks.
  4. Refer to DII webhook documentation for supported parameters and template examples.

Partner Notes

 

Additional Information

Internal Notes

  • Originated from case 2010762847.
  • Support and customer initially interpreted Test Webhook 400 responses as production alert failure.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.