AWS devopsagent documentation change
Summary
Replaced payload schema with reference to centralized webhook documentation
Security assessment
Content reorganization pointing to existing security documentation. No new security information added.
Diff
diff --git a/devopsagent/latest/userguide/connecting-telemetry-sources-connecting-datadog.md b/devopsagent/latest/userguide/connecting-telemetry-sources-connecting-datadog.md index 2bbb10732..036fdffb8 100644 --- a//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-datadog.md +++ b//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-datadog.md @@ -104,27 +104 @@ Using the Webhook URL and API Key you can configure Datadog to send events to tr -To ensure that events sent can be used by the DevOps Agent, make sure that the data transmitted to the webhook matches the data schema specified below. Events that do not match this schema may be ignored by DevOps Agent. - -Set the method and the headers - - - method: "POST", - headers: { - "Content-Type": "application/json", - "Authorization": "Bearer <Token>", - }, - - -Send the body as a JSON string. - - - { - eventType: 'incident'; - incidentId: string; - action: 'created' | 'updated' | 'closed' | 'resolved'; - priority: "CRITICAL" | "HIGH" | "MEDIUM" | "LOW" | "MINIMAL"; - title: string; - description?: string; - timestamp?: string; - service?: string; - // The original event generated by service is attached here. - data?: object; - } +Datadog webhooks use bearer token authentication. For the complete webhook request format, payload schema, and example code, see [Invoking DevOps Agent through Webhook](./configuring-capabilities-for-aws-devops-agent-invoking-devops-agent-through-webhook.html). Use the Version 2 (Bearer token authentication) examples, setting the `Authorization: Bearer <Token>` header with the API Key from Step 2.