Datadog/dora

@webframp/datadog/dorav2026.10.21.1· Apache-2.0· 5d agoBEHAVIORS

01README

Datadog DORA Metrics — deployment frequency, lead time, MTTR, and change failure rate

02Release Notes

2026.10.21.1

Changed: The README now shows how to store the API key and application key in a datadog vault and wire them with ${{ vault.get("datadog", "API_KEY") }} and ${{ vault.get("datadog", "APP_KEY") }}. The previous example passed DD_API_KEY and DD_APP_KEY as literal global arguments, which swamp rejects for sensitive arguments.

Changed: The apiKey and appKey descriptions now say to supply them with a vault.get expression. Both were already marked sensitive.

Upgrade note: Documentation and argument descriptions only. Methods, arguments, resource schemas and stored data are unchanged.

03Behaviors1

@webframp/datadog/dorav2026.10.21.1datadog/dora.ts

Global Arguments

Argument	Type	Required	Description
apiKey	string	yes	Datadog API key (DD-API-KEY). Wire it with ${{ vault.get("datadog", "API_KEY") }}; never pass the literal value.
appKey	string	yes	Datadog application key (DD-APPLICATION-KEY). Wire it with ${{ vault.get("datadog", "APP_KEY") }}; never pass the literal value.
site?	enum	no	Datadog site

fn create_dora_deployment(custom_tags?: unknown, env?: string, finished_at: number, git?: unknown, service: string, started_at: number, team?: string, version?: string)

Send a deployment event

Argument	Type	Required	Description
custom_tags?	unknown	no
env?	string	no	Environment name to where the service was deployed.
finished_at	number	yes	Unix timestamp when the deployment finished. It must be in nanoseconds, milli...
git?	unknown	no
service	string	yes	Service name.
started_at	number	yes	Unix timestamp when the deployment started. It must be in nanoseconds, millis...
team?	string	no	Name of the team owning the deployed service. If not provided, this is automa...
version?	string	no

fn delete_dora_deployment(deployment_id: string)

Delete a deployment event

Argument	Type	Required	Description
deployment_id	string	yes	The ID of the deployment event to delete.

fn list_dora_deployments(from?: string, limit?: number, query?: string, sort?: string, to?: string)

Get a list of deployment events

Argument	Type	Required	Description
from?	string	no	Minimum timestamp for requested events.
limit?	number	no	Maximum number of events in the response.
query?	string	no	Search query with event platform syntax.
sort?	string	no	Sort order (prefixed with `-` for descending).
to?	string	no	Maximum timestamp for requested events.

fn patch_dora_deployment_by_version(change_failure: boolean, env: string, remediation?: unknown, service: string, version: string)

Mark a deployment as failed by version

Argument	Type	Required	Description
change_failure	boolean	yes	Indicates whether the deployment resulted in a change failure.
env	string	yes	The environment the deployment was performed in.
remediation?	unknown	no
service	string	yes	The name of the service that was deployed.
version	string	yes	The version deployed. This can be seen in the Service Catalog or in the APM D...

fn get_dora_deployment(deployment_id: string)

Get a deployment event

Argument	Type	Required	Description
deployment_id	string	yes	The ID of the deployment event.

fn patch_dora_deployment(deployment_id: string, change_failure?: boolean, remediation?: unknown)

Mark a deployment as failed by ID

Argument	Type	Required	Description
deployment_id	string	yes	The ID of the deployment event.
change_failure?	boolean	no	Indicates whether the deployment resulted in a change failure.
remediation?	unknown	no

fn create_dora_failure(custom_tags?: unknown, env?: string, finished_at?: number, git?: unknown, name?: string, services?: array, severity?: string, started_at: number, team?: string, version?: string)

Send an incident event

Argument	Type	Required	Description
custom_tags?	unknown	no
env?	string	no	Environment name that was impacted by the incident.
finished_at?	number	no	Unix timestamp when the incident finished. It must be in nanoseconds, millise...
git?	unknown	no
name?	string	no	Incident name.
services?	array	no	Service names impacted by the incident. If possible, use names registered in ...
severity?	string	no	Incident severity.
started_at	number	yes	Unix timestamp when the incident started. It must be in nanoseconds, millisec...
team?	string	no	Name of the team owning the services impacted. If possible, use team handles ...
version?	string	no

fn delete_dora_failure(failure_id: string)

Delete an incident event

Argument	Type	Required	Description
failure_id	string	yes	The ID of the incident event to delete.

fn list_dora_failures(from?: string, limit?: number, query?: string, sort?: string, to?: string)

Get a list of incident events

Argument	Type	Required	Description
from?	string	no	Minimum timestamp for requested events.
limit?	number	no	Maximum number of events in the response.
query?	string	no	Search query with event platform syntax.
sort?	string	no	Sort order (prefixed with `-` for descending).
to?	string	no	Maximum timestamp for requested events.

fn get_dora_failure(failure_id: string)

Get an incident event

Argument	Type	Required	Description
failure_id	string	yes	The ID of the incident event.

Resources

dora_deployment(infinite)— Send a deployment event

dora_deployments(infinite)— Get a list of deployment events

patch_dora_deployment_by_version(infinite)— Mark a deployment as failed by version

patch_dora_deployment(infinite)— Mark a deployment as failed by ID

dora_failure(infinite)— Send an incident event

dora_failures(infinite)— Get a list of incident events

04Previous Versions12

2026.10.14.1Apache-2.0(was none)Oct 14, 2026

2026.10.14.1

Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.

Upgrade note: Metadata only. No code, schema, or behavioral changes.

2026.10.07.1

Added: patch_dora_deployment_by_version marks a deployment as failed by service, env, and version (PATCH /api/v2/dora/deployments), with a matching patch_dora_deployment_by_version resource.

Fixed: The shared API helper no longer throws on a successful response with an empty body (such as 202 Accepted); it returns an empty result. Datadog answers the by-version patch with an empty 202, which the previous helper failed to parse. Paginated list requests tolerate an empty page body the same way. A body that is not valid JSON now fails with an error naming the HTTP method, path, and status, with a snippet of the body.

Changed: The description of patch_dora_deployment now reads "Mark a deployment as failed by ID" (previously "Patch a deployment event"). Behavior is unchanged.

Upgrade note: Additive changes only; existing stored resources remain valid and no migration is needed.

2026.09.18.1Sep 20, 2026

2026.09.18.1

Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the repo. No behavioral changes in this extension.

2026.09.15.1Sep 15, 2026

2026.09.15.1

Changed: Bump zod 4.4.3 → 4.6.5

2026.09.08.1

Added: Initial code-generated release of @webframp/datadog/dora with 9 methods covering the Datadog dora API surface.

2026.09.08.1Sep 9, 2026

2026.09.08.1

Added: Initial code-generated release of @webframp/datadog/dora with 9 methods covering the Datadog dora API surface.

2026.08.28.2Aug 28, 2026

2026.08.28.2

Hardened codegen: instance names sanitized against path traversal; string schema patterns emit regex validation; output schemas passthrough unknown fields.

updated labels

2026.08.28.1Aug 28, 2026

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.2

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.2Aug 27, 2026

2026.08.26.2

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.25.1Aug 26, 2026

2026.08.25.1

Changed: Updated labels for improved extension discoverability. Added cross-cutting category labels (security, observability, finops, infrastructure, networking, compliance, devops, ai, incident-response) where applicable.

updated labels

2026.08.24.1Aug 24, 2026

2026.08.24.1

Added: Output metadata attributes for observability.

durationMs: Method execution duration in milliseconds.
collectedBy: Extension name that produced the data.
fetchedAt: ISO 8601 timestamp when data was fetched (added to resources that previously lacked it).

2026.08.21.2Aug 22, 2026

2026.08.21.2

Changed: Every Datadog API call made by this model (via the shared _lib/api.ts helper) now names the HTTP method and path in its error message, instead of a bare "Datadog API HTTP 500: ...". A failure now reads, for example, Datadog API POST /api/v2/dora/deployment failed with HTTP 500: ... rather than just the status code and response body. Network-level failures (DNS, connection reset, etc.) that previously surfaced as a raw TypeError now also say which Datadog operation was being attempted.

No changes to method arguments, resource schemas, or successful-call behavior — only error paths are affected.

2026.08.21.1Aug 21, 2026

2026.08.21.1

Changed: Schema-only tightening pass, no behavioral change.

Added .min(1) to apiKey and appKey in the global arguments, and to deployment_id/failure_id in the delete, get, and patch method arguments, so empty identifiers are rejected before making an API call.
Added .describe() to previously undocumented fields: the JSON:API type field on the deployment/failure creation resource schemas, the nested git.commit_sha/git.repository_id/git.repository_url fields, and the custom_tags/git/remediation arguments on the create_dora_deployment, create_dora_failure, and patch_dora_deployment methods.