[appsec] system tests for agentic onboarding runtime detection#7320
Conversation
|
|
🎉 All green!🧪 All tests passed 🔗 Commit SHA: 18082e8 | Docs | Datadog PR Page | Give us feedback! |
|
📊 dbt CICD (full report) Impact Lineage Error detailsError fetching impact lineage results. Drift Detection Error detailsError fetching drift detection results. 🔗 Commit SHA: c900870 | Docs | Give us feedback! |
c68ce33 to
322e797
Compare
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 322e797c4c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 70986e693b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
RFC-1110: validate the appsec.agentic_onboarding boolean reported in app-started telemetry when DD_APPSEC_AGENTIC_ONBOARDING is set (true when AppSec is active at startup, false otherwise). Reuses the existing telemetry scenarios; tests are missing_feature until tracers implement it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The signal targets the 7 application tracers (RFC-1110); C++ proxies are out of scope, so the test is irrelevant there (cpp_kong already blankets tests/appsec as irrelevant). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- assert origin=env_var in the AppSec-disabled (false) case so the entry is driven by the flag itself, not a default/product-state config - clarify docstrings: the signal may ride app-started or the subsequent app-client-configuration-change (RFC-1110), both intentionally accepted Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- exact-case match on the config key (intake normalization relies on it) - assert the raw DD_APPSEC_AGENTIC_ONBOARDING key is never transmitted - strict boolean checks (reject numeric 0/1 via `is`) - precise return typing; drop redundant comment - cpp: drop redundant cpp_httpd entry (blanket already covers), use bare missing_feature for cpp/cpp_nginx (RFC-1110 targets the 7 app tracers) - python: feature merged on main -> activate at v4.12.0 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
70986e6 to
83de56e
Compare
- #4: replace entries[-1] with a loop asserting every reported entry is consistent (origin=env_var + expected bool) — catches contradictory/ duplicate reports without a count assertion that would flake on prefork/multiprocess weblogs - python: activate at v4.13.0-rc1 (feature merged on main) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…telemetry Some tracers report telemetry configuration entries under the raw dotted name (appsec.agentic_onboarding) while others (e.g. Java) normalize it to the env-var form (DD_APPSEC_AGENTIC_ONBOARDING, uppercased with dots -> underscores). Accept either, matching the convention used by other telemetry tests (e.g. ["DD_APPSEC_ENABLED", "appsec.enabled"]). Also drops the incorrect "raw key must not be reported" assertions from #7320: the two names are just the raw and normalized forms of the same config, not a forbidden separate entry. Presence-only refers to the env-var's value never being read, not to a second telemetry entry. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
APPSEC-69171
System tests for RFC-1110 (Agentic Onboarding Runtime Detection, feature #563): validate the
appsec.agentic_onboardingboolean inapp-startedtelemetry whenDD_APPSEC_AGENTIC_ONBOARDINGis set —truewhen AppSec is active at startup,falseotherwise (flag is presence-only).Reuses existing telemetry scenarios; the two tests are
missing_featureuntil each tracer implements the signal.🤖 Generated with Claude Code