Document agentless Feature Flags delivery for Java and Node.js

[leoromanovsky]

Motivation

Java and Node.js Feature Flags are adding a Datadog-managed CDN configuration source that does not require a Datadog Agent. The documentation currently presents Agent Remote Configuration as the server SDK delivery path and describes no-Agent serverless delivery as unsupported.

Customers need the new default explained before adopting the next minor releases, including exact minimum versions and the initial limitation that no-Agent deployments do not deliver exposure or aggregate flagevaluation events.

Related implementations:

• Add agentless Feature Flagging configuration source dd-trace-java#11892
• feat(openfeature): add agentless Feature Flagging configuration source dd-trace-js#9402

Changes

• Add a Server SDK Configuration Sources concept page and surface it first in the Server SDK navigation.
• Revise the Server SDK overview and serverless guidance to present agentless configuration delivery as the default where supported.
• Document proposed minimum versions: Java 1.65.0, Node.js v5 5.116.0, and Node.js v6 6.5.0.
• Add agentless and explicit Agent Remote Configuration setup details to the Java and Node.js pages.
• State consistently that the initial agentless releases support configuration delivery and local flag evaluation, but not agentless exposure or aggregate flagevaluation event delivery.

Decisions

• Lead with agentless delivery because it is the default for supported Server SDK versions.
• Keep remote_config as an explicit Agent-managed alternative.
• List Node.js minimums per major release line instead of using a single ambiguous lower bound.
• Keep flag configuration delivery separate from APM and serverless telemetry setup.
• Treat offline customer-provided UFC as a future mode, not an available option.

Validation

• git diff --check
• YAML parsing for the navigation update
• Frontmatter parsing for all changed content pages
• Vale validation with no findings on added lines
• Local link and secret scans for the changed files

A full local Hugo render reached site generation but stopped in unrelated account-management pages because the shared header asset pipeline passed an empty resource slice to resources.Concat. None of the changed Feature Flags pages appeared in the render error.

[github-actions]

Preview links (active after the build_preview check completes)

New or renamed files

• https://docs-staging.datadoghq.com/leo.romanovsky/agentless-feature-flags-docs/feature_flags/concepts/configuration_sources

Modified Files

• https://docs-staging.datadoghq.com/leo.romanovsky/agentless-feature-flags-docs/feature_flags/
• https://docs-staging.datadoghq.com/leo.romanovsky/agentless-feature-flags-docs/feature_flags/concepts/
• https://docs-staging.datadoghq.com/leo.romanovsky/agentless-feature-flags-docs/feature_flags/implementation_patterns/serverless
• https://docs-staging.datadoghq.com/leo.romanovsky/agentless-feature-flags-docs/feature_flags/server/
• https://docs-staging.datadoghq.com/leo.romanovsky/agentless-feature-flags-docs/feature_flags/server/java
• https://docs-staging.datadoghq.com/leo.romanovsky/agentless-feature-flags-docs/feature_flags/server/nodejs

[datadog-datadog-us1-prod]

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/documentation | build_preview     

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: d4bf0d2 | Docs | Datadog PR Page | Give us feedback!}