Skip to main content
NetApp Knowledge Base

PagerDuty webhook notifications from Data Infrastructure Insights fail with HTTP 400 Bad Request

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

Applies to

  • Data Infrastructure Insights (DII)

Issue

  • PagerDuty webhook notifications from Data Infrastructure Insights fail with HTTP 400 Bad Request.
  • The DII webhook editor shows Error calling Webhook (status: 400).
  • Alerts are not delivered to PagerDuty even though a custom routing key secret may be configured.

Cause

  • PagerDuty Events API v2 requires a valid Integration Key in the routing_key JSON field.
  • The DII webhook message body sends an empty routing_key value (for example "routing_key": "") or does not reference the configured custom secret.
  • PagerDuty rejects the payload and returns HTTP 400.

Solution

  1. In PagerDuty, open the target service and copy the Events API v2 Integration Key.
  2. In DII, go to Admin > Notifications > Webhooks and edit the PagerDuty webhook.
  3. Under Custom Parameters and Secrets, create or update a secret named routingKey with the Integration Key value.
  4. In the message body JSON, reference the secret in the routing_key field:
    "routing_key": "%%routingKey%%",
  5. Save the webhook.
  6. Validate delivery by triggering a real monitor alert and reviewing the Status and Last Reported columns on the Webhooks list page.

Partner Notes

 

Additional Information

  • See Webhook example for PagerDuty for field mapping and setup guidance.
  • Note: The DII Test Webhook button does not substitute parameters. A 400 response on test alone does not confirm production delivery is broken.

Internal Notes

  • Originated from case 2010762847.
  • Customer had a valid custom secret configured but the message body used an empty routing_key value instead of %%routingKey%%.

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.