Skip to main content

Datadog/slos

@webframp/datadog/slosv2026.10.21.1· Apache-2.0· 5d agoBEHAVIORS
01README

Datadog SLOs — service level objective definitions, status, and history

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/slosv2026.10.21.1datadog/slos.ts

Global Arguments

ArgumentTypeDescription
apiKeystringDatadog API key (DD-API-KEY). Wire it with ${{ vault.get("datadog", "API_KEY") }}; never pass the literal value.
appKeystringDatadog application key (DD-APPLICATION-KEY). Wire it with ${{ vault.get("datadog", "APP_KEY") }}; never pass the literal value.
site?enumDatadog site
fn get_slo_status(slo_id: string, from_ts?: number, to_ts?: number, disable_corrections?: boolean)
Get SLO status
ArgumentTypeDescription
slo_idstringThe ID of the SLO.
from_ts?numberThe starting timestamp for the SLO status query in epoch seconds.
to_ts?numberThe ending timestamp for the SLO status query in epoch seconds.
disable_corrections?booleanWhether to exclude correction windows from the SLO status calculation. Defaul...

Resources

slo_status(infinite)— Get SLO status
04Previous Versions10
2026.10.14.1Apache-2.0(was none)

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

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. 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. Rate-limit retry no longer breaks on a non-numeric Retry-After header; it waits 5 seconds instead.

Upgrade note: Only the shared helper changed. No methods, arguments, schemas, or resources changed, so no migration is needed and existing stored resources remain valid.

2026.09.18.1

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.1

2026.09.15.1

Changed: Bump zod 4.4.3 → 4.6.5

2026.08.28.2

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

2026.08.28.2

2026.08.28.2

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

Modified 1 behaviors

2026.08.28.1

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

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.24.1

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

2026.08.21.2

Changed: Error messages and input validation are more specific.

  • API errors now name the HTTP method and path that was attempted (e.g. Datadog API HTTP 404: GET /api/v2/slo/abc-123/status) instead of just the raw status code and response body.
  • A network-level failure (DNS error, connection reset, timeout) reaching the Datadog API now raises Datadog API request failed: <METHOD> <path>: <reason> instead of an unlabeled fetch error.
  • report_id and slo_id are now rejected up front if empty, instead of building a malformed request path.
  • create_slo_report_job now rejects an empty query, and rejects to_ts values that are not after from_ts, before making a request — previously an inverted or zero-width time range would be sent to Datadog and fail (or silently return an empty report) with no explanation of why.

No changes to request/response shapes or existing successful-path behavior.

2026.08.21.1

Changed: Tightened and clarified Zod schemas as part of a repo-wide schema audit.

  • Added .min(1) to apiKey and appKey in the global arguments schema — both are sent directly as request headers, and an empty value would never be accepted by the Datadog API.
  • Added a description to the previously undocumented interval argument on create_slo_report_job.

No behavioral changes — these are documentation and validation tightenings only.

2026.07.20.11

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

2026.08.21.1

2026.08.21.1

Changed: Tightened and clarified Zod schemas as part of a repo-wide schema audit.

  • Added .min(1) to apiKey and appKey in the global arguments schema — both are sent directly as request headers, and an empty value would never be accepted by the Datadog API.
  • Added a description to the previously undocumented interval argument on create_slo_report_job.

No behavioral changes — these are documentation and validation tightenings only.

2026.07.20.11

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

2026.07.20.11

2026.07.20.11

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

05Stats
A
100 / 100
Downloads
36
Archive size
12.3 KB
  • 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
  • License2/2earned
  • Verified public repository2/2earned
06Platforms
07Labels