Datadog/logs

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

01README

Datadog Logs — log search, aggregation, and analytics

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/logsv2026.10.21.1datadog/logs.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 submit_log(ddtags?: string, entries: array)

Send logs

Argument	Type	Required	Description
ddtags?	string	no	Log tags can be passed as query parameters with `text/plain` content type.
entries	array	yes	Array of items to submit

fn aggregate_logs(compute?: array, filter?: unknown, group_by?: array, options?: unknown, page?: unknown)

Aggregate events

Argument	Type	Required	Description
compute?	array	no	The list of metrics or timeseries to compute for the retrieved buckets.
filter?	unknown	no
group_by?	array	no	The rules for the group by
options?	unknown	no
page?	unknown	no

fn list_logs_get(filter_query?: string, filter_indexes?: string, filter_from?: string, filter_to?: string, filter_storage_tier?: string, sort?: string)

Search logs (GET)

Argument	Type	Required	Description
filter_query?	string	no	Search query following logs syntax.
filter_indexes?	string	no	For customers with multiple indexes, the indexes to search. Defaults to '*' w...
filter_from?	string	no	Minimum timestamp for requested logs.
filter_to?	string	no	Maximum timestamp for requested logs.
filter_storage_tier?	string	no	Specifies the storage type to be used
sort?	string	no	Order of logs in results.

fn list_logs(filter?: unknown, options?: unknown, page?: unknown, sort?: unknown)

Search logs (POST)

Argument	Type	Required
filter?	unknown	no
options?	unknown	no
page?	unknown	no
sort?	unknown	no

Resources

submit_log(infinite)— Send logs

aggregate_logs(infinite)— Aggregate events

logs_get(infinite)— Search logs (GET)

logs(infinite)— Search logs (POST)

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

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.

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.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/logs with 4 methods covering the Datadog logs API surface.

2026.09.08.1Sep 9, 2026

2026.09.08.1

Added: Initial code-generated release of @webframp/datadog/logs with 4 methods covering the Datadog logs 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/logs 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.

submit_log now rejects an empty entries array at validation time with a clear "at least 1 element" error, instead of silently sending a no-op request to the Datadog Logs API.

No other changes to method arguments, resource schemas, or successful-call behavior.

2026.08.21.1Aug 21, 2026

2026.08.21.1

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

Added .min(1) to apiKey/appKey in the global arguments, so empty credentials are rejected before making an API call.
Added .describe() to the previously undocumented filter, options, and page arguments on aggregate_logs, and the filter, options, page, and sort arguments on list_logs.