Bugr or not? The "client" field processing via Event API (https://events.pagerduty.com/v2/enqueue)


I have a payload that successfully sends alerts via https://events.pagerduty.com/v2/enqueue

But if I specify in my JSON “Datadog” in the value of the "client" field, then the processing of alerts breaks.
In particular, the Summary becomes like this “(Incident triggered via the API)

And if I specify any value other than “Datadog” (even in a different register, for example, “DataDog”), then everything works again!

I have no other incoming event processing inside the PD.

Please tell me:

  • Is this normal behaviour or a bug?
  • Where can I read about what value cannot be used in the client field?

JSON example in a dropdown block below:

  "client": "DataDog",
  "client_url": "https://app.datadoghq.com/monitors/XXXXXX",
  "event_action": "trigger",
  "payload": {
    "summary": "Redhsift overloaded",
    "source": "central-region-dc-01:cluster/redhsift-prod-003",
    "severity": "warning",
    "component": "redshift",
    "group": "production",
    "class": "infrastructure",
    "custom_details": {
      "ping time": "1500ms",
      "load avg": 0.75
  "routing_key": "samplekey1here",
  "dedup_key": "samplekey2here",
  "images": [
      "src": "https://p.datadoghq.com/.../.../.../some.png",
      "href": "https://app.datadoghq.com/monitors/XXXXXX",
      "alt": "Snapshot of metric"
  "links": [
      "href": "https://my.atlassian.net/wiki/",
      "text": "Diagnostic instructions"

This behaviour can be seen in the screenshots:

"client": "DataDog",

"client": "Datadog",

We have internal event transformers that are triggering off of the client field name and expect the Event v1 format. If you want to send a custom Event v2 payload, suggest using something other than “Datadog” like “Datadog Custom”.