Datadog

Resource evaluation filters are set per cloud account (the public resource evaluation filters guide, pinned under datadog.docs), and this data set's Datadog organization has no AWS, Azure or Google Cloud account integrated, so the filter map is empty; id and type take the document's own example `csm_resource_filter`.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data, so a search over them matches nothing and Datadog returns the empty list.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud SIEM or security data configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/posture_management/findings on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/security_monitoring/configuration/critical_assets on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/security_monitoring/configuration/integration_config on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/security_monitoring/configuration/suppressions on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no Cloud SIEM or security data at all, so no Cloud SIEM or security record id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v2/security_monitoring/datasets on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/security_monitoring/datasets on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no Cloud SIEM or security data at all, so no Cloud SIEM or security record id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

generate — Datadog's own catalogue (Cloud SIEM's default detection rules), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (Cloud SIEM's default detection rules), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

refuse — Entailed by the empty /api/v2/security_monitoring/signals on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/security_monitoring/signals on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

generate — Datadog's own catalogue (the default security inbox rules), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

refuse — Entailed by the empty /api/v2/security/findings/automation/due_date_rules on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/security/findings/automation/mute_rules on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/security/findings/automation/ticket_creation_rules on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no Cloud SIEM data, so no indicator of compromise resolves, and this operation documents a 404 for one that does not: the answer is that 404.

refuse — Entailed by the empty /api/v2/security/vulnerabilities/notification_rules on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/siem-historical-detections/jobs on this host: no Cloud SIEM or security record id resolves, so the answer is this operation's documented 404.

generate — Datadog's own catalogue (the static analysis code-generation rulesets), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (the static analysis rulesets), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (the secret scanning rules), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (the static analyser's parser binaries), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

No custom usage report was ever generated for this data set's Datadog organization, so the daily report list is empty.

This data set's Datadog organization never used Log Management's analysed logs (security), so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

This data set's Datadog organization never used serverless monitoring (AWS Lambda), so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

This data set's Datadog organization never used Cloud Security Posture Management, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

This data set's Datadog organization never used Database Monitoring, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

Served to the org admin this caller is (ruling Q8) from the host table (hello-22 traces canon; decisions/2026-10-24-1632-datadog-traces-and-hosts.md; an artifact before hello-22 answers the generation gap): per hour, the hosts up in it, each running the Agent and a tracer (every service is traced); cloud and container counts are omitted, never zero.

Served to the org admin this caller is (ruling Q8): Incident Management's monthly active users are the distinct people on this data set's incidents (the commander, the paged and the responders), counted per hour from the incident rows.

This data set's Datadog organization never used IoT monitoring, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

Served to the org admin this caller is (ruling Q8; orchestrator ruling of 2026-10-24): the same two held products per month, plus indexed_spans_usage from hello-22 (host counts have no monthly figure the document defines, so they are not attributed by month), broken down by service and team, with each tag group's share of the month as the percentage.

This data set's Datadog organization never used Network Performance Monitoring, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

This data set's Datadog organization never used Continuous Profiler, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

This data set's Datadog organization never used RUM sessions, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

This data set's Datadog organization never used network device (SNMP) monitoring, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

This data set's Datadog organization never used Synthetic Monitoring, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

This data set's Datadog organization never used Synthetic browser tests, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

This data set's Datadog organization never used traced Lambda invocations, so its usage list for any period is empty (provisional: whether Datadog zero-fills the hours instead is UNVERIFIED).

refuse — Entailed by the empty /api/v1/daily_custom_reports on this host: no usage id resolves, so the answer is this operation's documented 404.

generate — Hosts and spans are counted now (hello-22), but each billable entry requires the billing plan, the committed units and the share of the month billed, which this data set does not hold (a price list); any value here would be invented.

generate — A figure Datadog computes (log counts by index, which needs the default index (UNVERIFIED)) from usage this data set does not record; any value here would be invented.

generate — A figure Datadog computes (custom metric counts, which needs Datadog's own split between custom and trace metrics) from usage this data set does not record; any value here would be invented.

generate — Fixed Datadog vocabulary the founder ruled servable (Q9/Q13, 2026-10-23), but neither the pinned documents nor Datadog's public documentation publishes the billing dimensions (which of them count as active for this organization is itself unstated) in full (checked 2026-10-23, orchestrator ruling 3), so serving it would invent the rest.

generate — Fixed Datadog vocabulary the founder ruled servable (Q9/Q13, 2026-10-23), but neither the pinned documents nor Datadog's public documentation publishes the billing dimension mapping in full (checked 2026-10-23, orchestrator ruling 3), so serving it would invent the rest.

generate — A cost figure: Datadog prices usage with its own list prices (the pinned document: "Prices are public list prices"), which this data set does not hold, so any amount here would be invented.

generate — The usage_type names this endpoint reports per product family are not published in the pinned documents (UNVERIFIED), so the v1 incident-management and logs rows carry this data set's usage instead.

generate — A Datadog-side setting (product quotas) whose default value the pinned documents do not state; answering it would invent the value.

generate — Fixed Datadog vocabulary the founder ruled servable (Q9/Q13, 2026-10-23), but neither the pinned documents nor Datadog's public documentation publishes the usage attribution types in full (checked 2026-10-23, orchestrator ruling 3), so serving it would invent the rest.

An aggregation over this data set's Datadog organization, which holds no Cloud Cost Management records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

An aggregation over this data set's Datadog organization, which holds no Cloud Cost Management records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

An aggregation over this data set's Datadog organization, which holds no Cloud Cost Management records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

An aggregation over this data set's Datadog organization, which holds no Cloud Cost Management records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

An aggregation over this data set's Datadog organization, which holds no Cloud Cost Management records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

An aggregation over this data set's Datadog organization, which holds no Cloud Cost Management records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Cloud Cost Management configured, so the list Datadog returns for it is empty.

refuse — This data set's Datadog organization has no Cloud Cost Management at all, so no Cloud Cost Management id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v2/cost/aws_cur_config on this host: no Cloud Cost Management id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

refuse — This data set's Datadog organization has no Cloud Cost Management at all, so no Cloud Cost Management id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v2/cost/custom_costs on this host: no Cloud Cost Management id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/cost/tag_descriptions on this host: no Cloud Cost Management id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/cost/tag_keys on this host: no Cloud Cost Management id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/tags/enrichment on this host: no Cloud Cost Management id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

This data set's Datadog organization has no LLM Observability configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no LLM Observability configured, so the list Datadog returns for it is empty.

An aggregation over this data set's Datadog organization, which holds no LLM Observability records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

LLM Observability was never connected to any LLM provider in this data set's Datadog organization, so the configured accounts for every supported provider are the empty list.

This data set's Datadog organization has no LLM Observability configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/unstable/llm-obs/config/evaluators/custom on this host: no LLM Observability id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no LLM Observability at all, so no LLM Observability id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no LLM Observability at all, so no LLM Observability id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v2/llm-obs/v1/annotation-queues on this host: no LLM Observability id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/llm-obs/v1/annotation-queues on this host: no LLM Observability id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/llm-obs/v1/integrations/{integration}/accounts on this host: no LLM Observability id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

refuse — Entailed by the empty /api/v2/llm-obs/v1/prompts on this host: no LLM Observability id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

generate — The empty answer here still requires meta.elapsed, the time Datadog's query took, a measurement no document supplies; the request id and query status alone would be servable under ruling 4, but a zero elapsed would be a made-up measurement, so it is left uncovered.

refuse — LLM Observability topic discovery was never configured for this data set's Datadog organization, and this operation documents a 404 when no run exists: the answer is that 404.

refuse — LLM Observability topic discovery was never configured for this data set's Datadog organization, and this operation documents a 404 when no run exists: the answer is that 404.

generate — Datadog's own catalogue (LLM Observability topic discovery templates), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

refuse — LLM Observability topic discovery was never configured for this data set's Datadog organization, and this operation documents a 404 when no run exists: the answer is that 404.

refuse — This data set's Datadog organization has no LLM Observability at all, so no LLM Observability id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

This data set's Datadog organization has no Synthetic Monitoring tests configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Synthetic Monitoring tests configured, so the list Datadog returns for it is empty.

An aggregation over this data set's Datadog organization, which holds no Synthetic Monitoring test records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v1/synthetics/tests on this host: no Synthetic Monitoring test id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v1/synthetics/tests on this host: no Synthetic Monitoring test id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v1/synthetics/variables on this host: no Synthetic Monitoring test id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

generate — A Datadog-side setting (the on-demand concurrency cap) whose default value the pinned documents do not state; answering it would invent the value.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no Synthetic Monitoring test at all, so no Synthetic Monitoring test id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

No Datadog-side integration (a Slack channel or Jira issue created by Datadog) is attached to any incident in this data set, so each incident's integration list is empty.

No incident in this data set had a timestamp overridden by hand, so each incident's override list is empty.

This data set's Datadog organization has no incident impact fields configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no incident notification templates configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no incident rules configured, so the list Datadog returns for it is empty.

Served from the public responder-roles page (Datadog's public documentation, captured and sha-pinned under datadog.docs; orchestrator ruling 3 of 2026-10-23): the default Incident Commander role by its derived id.

generate — A postmortem Datadog's model writes on request; this data set holds no such text, and generating prose at request time is not something this replica does.

refuse — Entailed by the empty /api/v2/incidents/{incident_id}/relationships/todos on this host: no Incidents id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/incidents/config/notification-rules on this host: no Incidents id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/incidents/config/postmortem-templates on this host: no Incidents id resolves, so the answer is this operation's documented 404.

generate — Fixed Datadog vocabulary the founder ruled servable (Q9/Q13, 2026-10-23), but neither the pinned documents nor Datadog's public documentation publishes the organization's default incident type (its id, name and description) in full (checked 2026-10-23, orchestrator ruling 3), so serving it would invent the rest.

generate — A Datadog-side setting (per-incident-type organization settings) whose default value the pinned documents do not state; answering it would invent the value.

generate — The public property-fields page names the five default fields (Detection Method, Summary, Root Cause, Services, Teams), but each listed field requires its search metadata, type code, ordinal, creator and incident type, none of which is published; serving them would invent those (orchestrator ruling 3, checked 2026-10-23).

generate — Which tags queries actually used over a lookback window: Datadog computes it from its own query logs, which this data set does not record, so any list here would be invented.

generate — A cardinality delta Datadog computes between two of its own measurement windows; this data set records no such delta, so any figure here would be invented.

refuse — No metric in this data set has a tag configuration (Metrics without Limits was never set up), and this operation documents a 404 for a metric with none: the answer is that 404.

refuse — Historical metrics ingestion was never enabled for any metric in this data set's Datadog organization, so no configuration resolves and the answer is this operation's documented 404.

This data set's Datadog organization has no Experimentss configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Experimentss configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Experimentss configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Experimentss configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/experiments on this host: no Experiments id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/experiments on this host: no Experiments id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/experiments on this host: no Experiments id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/experiments/metric-collections on this host: no Experiments id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/experiments/metrics on this host: no Experiments id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/experiments/subject-types on this host: no Experiments id resolves, so the answer is this operation's documented 404.

This data set tracks work in Jira, not in Datadog Case Management, so a case search matches nothing and the list is empty.

This data set's Datadog organization has no Case Management cases, so the count is an object-shaped empty: one group per field named in group_bys, each with no values; data.type takes the document's own example `count` (clause a) and data.id is derived from the request (clause b) (ruling 4, decisions/2026-10-27-2126-datadog-documented-free-values.md).

This data set tracks work in Jira, not in Datadog Case Management, so no case project exists and the list is empty.

This data set's Datadog organization has no case project, so no saved case view exists and the list is empty.

refuse — Entailed by the empty /api/v2/cases on this host: no Case Management id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/cases on this host: no Case Management id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/cases/projects on this host: no Case Management id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/cases/projects on this host: no Case Management id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no AWS integration configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no AWS integration configured, so the list Datadog returns for it is empty.

An aggregation over this data set's Datadog organization, which holds no AWS integration records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

refuse — Entailed by the empty /api/v2/integration/aws/accounts on this host: no AWS integration id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/integration/aws/accounts on this host: no AWS integration id resolves, so the answer is this operation's documented 404.

generate — Datadog's own catalogue (the AWS namespaces Datadog can collect), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (the IAM permissions Datadog's AWS integration needs), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

Served to the org admin this caller is (ruling Q8) from person_credential: the one group token is this organization's API key (ruling Q14); name, created and creator read off the row, the key value is never served.

Served to the org admin this caller is (ruling Q8) from person_credential: every member's active personal token is an application key (ruling Q14).

Served to the org admin this caller is (ruling Q8) from person_credential: the one group token is this organization's API key (ruling Q14); last4 is hashed from the canonical id, never a key value.

Served to the org admin this caller is (ruling Q8) from person_credential: every member's active personal token is an application key (ruling Q14).

Served from person_credential: the current user is athena, the founding member (the Buildkite /v2/access-token precedent), and her active personal tokens are her application keys (ruling Q14).

This data set's Datadog organization issued no personal access tokens: each member's personal token is already served as an application key, and one canonical credential is not served as two grants (ruling Q14), so the list is empty.

refuse — Entailed by the empty /api/v2/personal_access_tokens on this host: no Key Management id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no Code Security (static analysis) data configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Code Security (static analysis) data configured, so the list Datadog returns for it is empty.

refuse — This data set's Datadog organization has no Code Security (static analysis) data at all, so no Code Security (static analysis) record id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v2/static-analysis/ai/rulesets on this host: no Code Security (static analysis) record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/static-analysis/ai/rulesets on this host: no Code Security (static analysis) record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/static-analysis/custom/rulesets on this host: no Code Security (static analysis) record id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/static-analysis/custom/rulesets on this host: no Code Security (static analysis) record id resolves, so the answer is this operation's documented 404.

No team in this data set's Datadog organization has member teams (every team is flat), so each team's member-team list is empty.

No team in this data set's Datadog organization has a link (a runbook or channel URL) configured, so each team's link list is empty.

No team in this data set's Datadog organization has a team notification rule, so each team's list is empty.

No team in this data set's Datadog organization is connected to an external team (the team connections list is empty) and it has no ServiceNow integration (the ServiceNow instance list is empty), so no team sync is configured for either documented source and the list is empty.

refuse — Entailed by the empty /api/v2/team-hierarchy-links on this host: no Teams id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/team/{team_id}/notification-rules on this host: no Teams id resolves, so the answer is this operation's documented 404.

SERVED 2026-10-27 (founder ruling F7, a rider on the hello-23 serving; decisions/2026-10-27-2306-hello-23-serving-rest.md): the person's channels derived from the contact methods the PagerDuty host serves for them. A phone channel per number their phone and SMS methods name, E.164 and its international form built from the 555-01xx fiction block, region US, verified when a served rule delivers on it, sms_subscribed_at the SMS method's creation; an email channel at the user's own address with formats html, the pinned document's declared default. Push methods are left out: Datadog requires a device and application name canon does not hold.

SERVED 2026-10-27 (founder ruling F7; decisions/2026-10-27-2306-hello-23-serving-rest.md): one rule per PagerDuty assignment rule of the person that delivers on a served channel: category from its urgency, delay_minutes from its start delay, voice or sms from its contact method's kind, and the channel that method maps to (include=channel adds it). Hand-off and status-update rules have no On-Call counterpart, and a rule on a push method goes with its channel.

generate — No routing rule is recorded in this data set: pages reach a team through its escalation policy, and a catch-all rule here would be invented.

An aggregation over this data set's Datadog organization, which holds no Product Analytics data records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

An aggregation over this data set's Datadog organization, which holds no Product Analytics data records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

This data set's Datadog organization has no Product Analytics events, so a journey matches no entity: records empty and total_count 0; entity takes the document's own example `session` (clause a, also the entity of the documented default join key @session.id) and data.id is derived from the request (clause b) (ruling 4, decisions/2026-10-27-2126-datadog-documented-free-values.md).

An aggregation over this data set's Datadog organization, which holds no Product Analytics data records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

An aggregation over this data set's Datadog organization, which holds no Product Analytics data records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

An aggregation over this data set's Datadog organization, which holds no Product Analytics data records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

This data set's status page is a Statuspage page (served on statuspage.sandboxapis.dev), not a Datadog status page, so Datadog's status page list is empty.

This data set's Datadog organization has no Datadog status page, so it has no maintenance and the list is empty.

refuse — Entailed by the empty /api/v2/statuspages on this host: no Status Pages id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

refuse — Entailed by the empty /api/v2/statuspages on this host: no Status Pages id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

refuse — Entailed by the empty /api/v2/statuspages on this host: no Status Pages id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

refuse — Entailed by the empty /api/v2/statuspages on this host: no Status Pages id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

An aggregation over this data set's Datadog organization, which holds no Model Lab project records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

This data set's Datadog organization has no Model Lab projects configured, so the list Datadog returns for it is empty.

generate — An aggregation over records this data set does not hold, so its honest answer is empty, but that empty answer still requires a response body, a value the pinned document leaves free (no fixed value, no default, and not a response id, which is derived from the request under the orchestrator ruling of 2026-10-24); left uncovered rather than guessed (orchestrator ruling of 2026-10-23).

refuse — This data set's Datadog organization has no Model Lab project, so there is no run to facet, and this operation documents a 404 for that case: the answer is that 404.

refuse — Entailed by the empty /api/v2/model-lab-api/projects on this host: no Model Lab project id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

refuse — Entailed by the empty /api/v2/model-lab-api/runs on this host: no Model Lab project id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no monitor notification rules configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no monitor templates configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/monitor/notification_rule on this host: no Monitors id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/monitor/template on this host: no Monitors id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no organization groups configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no organization groups configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no organization groups configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/org_group_memberships on this host: no organization group id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/org_group_policy_overrides on this host: no organization group id resolves, so the answer is this operation's documented 404.

This data set runs no Datadog Agent with tracer libraries reporting to Fleet Automation, so the tracer list is an object-shaped empty; data.type takes the document's own example `status` (clause a) and data.id is derived from the request (clause b) (ruling 4, decisions/2026-10-27-2126-datadog-documented-free-values.md).

This data set's Datadog organization has no Fleet Automation configured, so the list Datadog returns for it is empty.

refuse — This data set's Datadog organization has no Fleet Automation at all, so no Fleet Automation id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v2/fleet/agents on this host: no Fleet Automation id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/fleet/schedules on this host: no Fleet Automation id resolves, so the answer is this operation's documented 404.

This data set defines no service level objective (founder ruling Q6, 2026-10-23: none is invented), so the list Datadog returns is empty.

refuse — Entailed by the empty /api/v1/slo on this host: no Service Level Objectives id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v1/slo on this host: no Service Level Objectives id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v1/slo on this host: no Service Level Objectives id resolves, so the answer is this operation's documented 404.

refuse — No SLO report job was ever started for this data set's Datadog organization (it defines no SLO, ruling Q6), so no report id resolves and the answer is this operation's documented 404.

Served from the public permissions page (Datadog's public documentation, captured and sha-pinned under datadog.docs; orchestrator ruling 3 of 2026-10-23): the permissions of the managed role the member's organization role maps to.

generate — Which identity provider each user signs in with is a Datadog-side login fact this data set does not record; any answer here would be invented.

This data set's Datadog organization has no Agentless Scanning accounts configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no Agentless Scanning accounts configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/agentless_scanning/accounts/aws on this host: no Agentless Scanning account id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/agentless_scanning/accounts/gcp on this host: no Agentless Scanning account id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no App Builder apps configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/app-builder/apps on this host: no App Builder app id resolves, so the answer is this operation's documented 404.

generate — Datadog's own catalogue (App Builder blueprints), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (App Builder blueprints), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (Workload Protection's default agent rules), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (Workload Protection's default policies), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (the Workload Protection default policy file), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

generate — Datadog's own catalogue (Workload Protection's default agent rules), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

This data set's Datadog organization has no Google Chat integration configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/integration/google-chat/organizations on this host: no Google Chat integration id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/integration/google-chat/organizations on this host: no Google Chat integration id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/integration/google-chat/organizations on this host: no Google Chat integration id resolves, so the answer is this operation's documented 404.

An aggregation over this data set's Datadog organization, which holds no Governance Console control records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

generate — A Datadog-side setting (the Governance Console configuration) whose default value the pinned documents do not state; answering it would invent the value.

generate — Datadog's own catalogue (the Governance Console's built-in controls), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

refuse — Entailed by the empty /api/v2/governance/insights on this host: no Governance Console control id resolves, so the answer is this operation's documented 404.

SAML was never configured for this data set's Datadog organization (members sign in with Datadog accounts), so the configuration list is empty.

generate — The managed-organizations shape requires a description, a sharing mode and an app URL for the organization, none of which this data set holds; any value would be invented.

generate — Fixed Datadog vocabulary the founder ruled servable (Q9/Q13, 2026-10-23), but neither the pinned documents nor Datadog's public documentation publishes the organization configuration settings in full (checked 2026-10-23, orchestrator ruling 3), so serving it would invent the rest.

An aggregation over this data set's Datadog organization, which holds no RUM application records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

This data set's Datadog organization has no RUM applications configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no RUM applications configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/rum/applications on this host: no RUM application id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no Application Security (WAF) rules configured, so the list Datadog returns for it is empty.

Application Security was never enabled for any service in this data set's Datadog organization, so the list for any service is empty.

refuse — Entailed by the empty /api/v2/remote_config/products/asm/waf/exclusion_filters on this host: no Application Security (WAF) rule id resolves, so the answer is this operation's documented 404.

generate — Datadog's own catalogue (Application Security's default WAF policies), not something this data set did; copying it would serve vendor content (ruling of 2026-10-22).

refuse — Entailed by the empty /api/v2/csm/settings/hosts on this host: no Cloud Security ownership id resolves, so the answer is this operation's documented 404.

refuse — Entailed by the empty /api/v2/csm/settings/hosts on this host: no Cloud Security ownership id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no Cloud Security ownership at all, so no Cloud Security ownership id resolves, and the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

generate — An aggregation over records this data set does not hold, so its honest answer is empty, but that empty answer still requires data (its required id), a value the pinned document leaves free (no fixed value, no default, and not a response id, which is derived from the request under the orchestrator ruling of 2026-10-24); left uncovered rather than guessed (orchestrator ruling of 2026-10-23).

This data set's Datadog organization has no deployment gates configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no deployment gates configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/deployment_gates on this host: no deployment gate id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no deployment gate at all, so no deployment gate id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

An aggregation over this data set's Datadog organization, which holds no RUM audience data records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

An aggregation over this data set's Datadog organization, which holds no RUM audience data records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

An aggregation over this data set's Datadog organization, which holds no RUM audience data records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

refuse — The entity names a Product Analytics entity type (users, accounts), and Product Analytics was never set up in this data set's Datadog organization, so no entity of any type is populated and the answer is Datadog's 404, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator rulings of 2026-10-23 and 2026-10-24).

This data set's Datadog organization has no cloud authentication mappings configured, so the list Datadog returns for it is empty.

This data set's Datadog organization has no cloud authentication mappings configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/cloud_auth/github/intake_mapping on this host: no cloud authentication mapping id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no cloud account scanned by Agentless Scanning (the agentless scanning account lists are empty), so the host list is empty; page_index and page_size are the request's own page and size or the documented defaults 0 and 10 (clause c) (ruling 4, decisions/2026-10-27-2126-datadog-documented-free-values.md).

This data set's Datadog organization has no Cloud Security hosts configured, so the list Datadog returns for it is empty.

An aggregation over this data set's Datadog organization, which holds no Cloud Security host records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

refuse — No dashboard in this data set's Datadog organization is shared publicly, so no sharing token resolves and the answer is this operation's documented 404.

generate — Dashboard view counts Datadog computes from its own front-end analytics, which this data set does not record; any figure here would be invented.

Served from the public permissions page (Datadog's public documentation, captured and sha-pinned under datadog.docs; orchestrator ruling 3 of 2026-10-23): every permission it lists, by identifier, display label and group; no description prose.

Served from membership_role (ruling Q9): one managed role by its derived id.

Served from membership (ruling Q9): the members whose organization role maps to this managed role.

refuse — Entailed by the empty /api/v2/rum/applications on this host: no RUM retention filter id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

refuse — Entailed by the empty /api/v2/rum/applications on this host: no RUM retention filter id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

refuse — Entailed by the empty /api/v2/rum/applications on this host: no RUM retention filter id resolves, so the answer is Datadog's 404 for a resource that does not exist, documented platform-wide rather than on this operation (a reviewed deviation, orchestrator ruling of 2026-10-23).

This data set's Datadog organization has no scorecard campaigns configured, so the list Datadog returns for it is empty.

Served from the public scorecard configuration page (Datadog's public documentation, captured and sha-pinned under datadog.docs; orchestrator ruling 3 of 2026-10-23): the ten out-of-the-box rules by name, each under its scorecard, none custom.

Computed from the served outcomes (orchestrator ruling of 2026-10-24): passes over passes plus failures, by entity, rule, scorecard or team, with the unjudged rule-service pairs counted as no data. by-kind answers the coverage error: a kind has no field in the score schema but an entity relationship whose type Datadog does not publish.

This data set's Datadog organization has no ServiceNow integration configured, so the list Datadog returns for it is empty.

refuse — This data set's Datadog organization has no ServiceNow integration at all, so no ServiceNow integration id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v2/integration/servicenow/handles on this host: no ServiceNow integration id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no feature flags configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/feature-flags on this host: no feature flag id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no feature flag at all, so no feature flag id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

This data set's Datadog organization has no log restriction querys configured, so the list Datadog returns for it is empty.

No log restriction query exists in this data set's Datadog organization, so the queries applying to any user are the empty list.

refuse — Entailed by the empty /api/v2/logs/config/restriction_queries on this host: no log restriction query id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no Microsoft Teams integration configured, so the list Datadog returns for it is empty.

refuse — This data set's Datadog organization has no Microsoft Teams integration at all, so no Microsoft Teams integration id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — Entailed by the empty /api/v2/integration/ms-teams/configuration/workflows-webhook-handles on this host: no Microsoft Teams integration id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no network devices configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/ndm/devices on this host: no network device id resolves, so the answer is this operation's documented 404.

refuse — This data set's Datadog organization has no network device at all, so no network device id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — No Code Coverage report was ever uploaded for any repository, branch, commit or pull request in this data set's Datadog organization, so the summary asked for does not exist and the answer is this operation's documented 404.

refuse — No Code Coverage report was ever uploaded for any repository, branch, commit or pull request in this data set's Datadog organization, so the summary asked for does not exist and the answer is this operation's documented 404.

This data set's Datadog organization has no Confluent Cloud integration configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/integrations/confluent-cloud/accounts on this host: no Confluent Cloud integration id resolves, so the answer is this operation's documented 404.

SERVED 2026-10-27 (hello-23 deploymentServices, founder ruling F8; decisions/2026-10-27-2306-hello-23-serving-rest.md): one DORA deployment per successful production deployment and per service whose files its commit range changed, which is canon's deployment_service table rather than a split of the repository into six. started_at and finished_at are the deployment's, git.commit_sha its commit, service the slug this host names the service by, env production, version the release tag. A pair count is not a deployment count: GitLab's dora/metrics counts the deployments. An artifact before hello-23 answers the generation gap.

This data set's Datadog organization has no Digital Experience journeys, so a search over them matches nothing and Datadog returns the empty list.

refuse — This data set's Datadog organization has no Digital Experience journey at all, so no Digital Experience journey id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

This data set's Datadog organization has no Fastly integration configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/integrations/fastly/accounts on this host: no Fastly integration id resolves, so the answer is this operation's documented 404.

Error logs derived from the sampled error events: one log per event, with the service, the timestamp, the error group's type and message, and status error.

Error logs derived from the sampled error events: one log per event, with the service, the timestamp, the error group's type and message, and status error.

An aggregation over this data set's Datadog organization, which holds no log archive records: the honest answer is the response with its collections empty and its counts zero, never a figure (orchestrator ruling of 2026-10-23).

refuse — Entailed by the empty /api/v2/logs/config/archives on this host: no log archive id resolves, so the answer is this operation's documented 404.

This data set's Datadog organization has no reference tables configured, so the list Datadog returns for it is empty.

refuse — Entailed by the empty /api/v2/reference-tables/tables on this host: no reference table id resolves, so the answer is this operation's documented 404.

No report schedule exists in this data set's Datadog organization, so the schedules for any dashboard are the empty list.

refuse — This data set's Datadog organization has no report schedule at all, so no report schedule id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

This data set's Datadog organization has no RUM operations configured, so the list Datadog returns for it is empty.

refuse — This data set's Datadog organization has no RUM operation at all, so no RUM operation id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no service account at all, so no service account id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.

refuse — This data set's Datadog organization has no service account at all, so no service account id resolves, and this operation documents a 404 for an id that does not: the answer is that 404.