Datadog/dora
Datadog DORA Metrics — deployment frequency, lead time, MTTR, and change failure rate
2026.09.08.1
Added: Initial code-generated release of @webframp/datadog/dora with 9 methods covering the Datadog dora API surface.
Global Arguments
| Argument | Type | Description |
|---|---|---|
| apiKey | string | Datadog API key (DD-API-KEY) |
| appKey | string | Datadog application key (DD-APPLICATION-KEY) |
| site | enum | Datadog site |
| Argument | Type | Description |
|---|---|---|
| custom_tags? | unknown | |
| env? | string | Environment name to where the service was deployed. |
| finished_at | number | Unix timestamp when the deployment finished. It must be in nanoseconds, milli... |
| git? | unknown | |
| service | string | Service name. |
| started_at | number | Unix timestamp when the deployment started. It must be in nanoseconds, millis... |
| team? | string | Name of the team owning the deployed service. If not provided, this is automa... |
| version? | string |
| Argument | Type | Description |
|---|---|---|
| deployment_id | string | The ID of the deployment event to delete. |
| Argument | Type | Description |
|---|---|---|
| from? | string | Minimum timestamp for requested events. |
| limit? | number | Maximum number of events in the response. |
| query? | string | Search query with event platform syntax. |
| sort? | string | Sort order (prefixed with `-` for descending). |
| to? | string | Maximum timestamp for requested events. |
| Argument | Type | Description |
|---|---|---|
| deployment_id | string | The ID of the deployment event. |
| Argument | Type | Description |
|---|---|---|
| deployment_id | string | The ID of the deployment event. |
| change_failure? | boolean | Indicates whether the deployment resulted in a change failure. |
| remediation? | unknown |
| Argument | Type | Description |
|---|---|---|
| custom_tags? | unknown | |
| env? | string | Environment name that was impacted by the incident. |
| finished_at? | number | Unix timestamp when the incident finished. It must be in nanoseconds, millise... |
| git? | unknown | |
| name? | string | Incident name. |
| services? | array | Service names impacted by the incident. If possible, use names registered in ... |
| severity? | string | Incident severity. |
| started_at | number | Unix timestamp when the incident started. It must be in nanoseconds, millisec... |
| team? | string | Name of the team owning the services impacted. If possible, use team handles ... |
| version? | string |
| Argument | Type | Description |
|---|---|---|
| failure_id | string | The ID of the incident event to delete. |
| Argument | Type | Description |
|---|---|---|
| from? | string | Minimum timestamp for requested events. |
| limit? | number | Maximum number of events in the response. |
| query? | string | Search query with event platform syntax. |
| sort? | string | Sort order (prefixed with `-` for descending). |
| to? | string | Maximum timestamp for requested events. |
| Argument | Type | Description |
|---|---|---|
| failure_id | string | The ID of the incident event. |
Resources
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.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.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.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.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.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.1
Changed: Schema-only tightening pass, no behavioral change.
- Added
.min(1)toapiKeyandappKeyin the global arguments, and todeployment_id/failure_idin 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:APItypefield on the deployment/failure creation resource schemas, the nestedgit.commit_sha/git.repository_id/git.repository_urlfields, and thecustom_tags/git/remediationarguments on thecreate_dora_deployment,create_dora_failure, andpatch_dora_deploymentmethods.
2026.07.20.11
Added: Initial code-generated release of @webframp/datadog/dora with 9 methods covering the Datadog dora API surface.
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License declared1/1earned
- Verified public repository2/2earned