Skip to main content
Use the @bijection/connectors/datadog entrypoint to declare Datadog resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Monitors

pull: Monitor classifications with their evaluation

The following example matches configuration standard.

Configuration: standard

Case: datadog/monitors/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: datadog. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: monitors
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Events

pull: Events in a relative window

The following example matches configuration standard.

Configuration: standard

Case: datadog/events/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: datadog. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: events
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Metric query

query: One fixed-window metric query

The following example matches configuration standard.

Configuration: standard

Case: datadog/metrics/query/standard. Connection and resource configuration are declared by this exact case. Credential kind: datadog. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: series
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. A read-only observation feed. Nothing here submits a metric, creates or mutes a monitor, or schedules a downtime: the probed credential could not submit metrics, and a cancelled downtime was seen to revert to active, so an acknowledged effect is not a persisted one. The connection selects the Datadog site (site, for example datadoghq.com or datadoghq.eu); the API host is api.<site>. The probed credential is an OAuth bearer (datadog.credential). The documented DD-API-KEY plus DD-APPLICATION-KEY pair is two headers, which one credential envelope does not write. Identity is the organization’s public_id. monitors.pull pages by id_offset with the last monitor id until an empty page. A monitor is born No Data, so a state alone proves nothing: each record carries stateEstablishedAt (overall_state_modified, null until an evaluation established the state) and evaluated. evaluationDelaySeconds is Datadog’s decision-layer lateness. A monitor missing from a listing is not withdrawn: the search index lags deletion and no tombstone is declared. events.pull walks the v2 events list in a relative window by meta.page.after. This endpoint was not exercised by the probe; it is declared from Datadog’s published API. metrics.query runs one metric query over a closed window declared once, so a replay sends the same request. Datadog chooses the rollup from the window’s width, so each series record carries the intervalSeconds it used, beside its points as millisecond timestamps and JSON doubles. Datadog accepts points up to an hour late and silently overwrites a duplicate point, so a re-read of a recent window can change; a series absent from a later read is not withdrawn. Nothing here has run against Datadog or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.