Update Configuration Docs For Clarity

[mhlidd]

What Does This Do

Clarified instructions for introducing new configurations and noted auto-generated version in the Feature Parity Dashboard.

Motivation

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[datadog-datadog-prod-us1]

More details

Documentation-only PR improving clarity on configuration version assignment workflow. The original text was vague about when to use auto-generated versions from the Feature Parity Dashboard; I refined the language to explicitly describe the registration process and clarified that versions are auto-generated, not manually provided. No runtime code is affected—this reduces developer confusion and prevents incorrect version assignments in configuration metadata.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 8c5682a · What is Autotest? · Any feedback? Reach out in #autotest}

[sarahchen6]

Thanks for the update!

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.01 s	13.90 s	[+0.0%; +1.6%] (maybe worse)
startup:insecure-bank:tracing:Agent	12.95 s	13.02 s	[-1.3%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	16.85 s	16.63 s	[+0.3%; +2.4%] (maybe worse)
startup:petclinic:iast:Agent	16.82 s	16.87 s	[-1.0%; +0.5%] (no difference)
startup:petclinic:profiling:Agent	16.59 s	16.79 s	[-2.4%; -0.1%] (maybe better)
startup:petclinic:sca:Agent	16.93 s	16.77 s	[+0.1%; +1.8%] (maybe worse)
startup:petclinic:tracing:Agent	16.06 s	16.25 s	[-2.1%; -0.3%] (maybe better)

Commit:8c5682ab · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-15 19:14:13 UTC ℹ️ Start processing command /merge

---

2026-07-15 19:14:18 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-07-15 20:13:45 UTC ℹ️ MergeQueue: This merge request was merged