Repository navigation
Add agent debug logging for feature flag onboarding - #13091
gh-worker-dd-mergequeue-cf854d[bot] merged 7 commits into
Conversation
Replace the DiagnosticLogger wrappers with plain SLF4J loggers. Agent-side code logs through the tracer's internal logger, so it needs no isolation wrapper. The provider keeps isolation where an application logging backend is involved: debug diagnostics go through debugQuietly and DebugLoggingHook, which cache DD_TRACE_DEBUG and swallow logging and formatting failures. - Warn at provider construction when DD_TRACE_DEBUG is enabled but the application logger blocks DEBUG for datadog.trace.api.openfeature. - Report flags=missing for Remote Config payloads without a flags member, separately from an empty configuration. - Drop the racy inFlight shutdown field and the duplicate parser summary. - Update the README to match. Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Assert the debug logs that the Remote Configuration service emits when it starts, stops, receives a document and sees it removed. Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Move the received and removed logs of the Remote Configuration service after the subscribers are notified, so that a failing logging backend cannot keep a configuration document from being delivered. Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Assert, with a subscriber, that the received log of the Remote Configuration service comes after the document is delivered. Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Hooray! Reviewed commit: ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback". |
This comment has been minimized.
This comment has been minimized.
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
There was a problem hiding this comment.
More details
Document diagnostics preserve subscriber delivery order and safely handle null removal events. The completed static review identified no actionable defects.
🤖 Bits Code Review · Commit e71a07a
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
5ca1c1f
into
master
Port #13091 from master: log the Feature Flagging system start and initialization failure, and the Remote Configuration source lifecycle and documents, once they are delivered.

What Does This Do
Adds DEBUG logs to the agent side of Feature Flagging:
FeatureFlaggingSystem: logs that the product is enabled (with the environment) and, if the backend fails to start, the type of the failure.RemoteConfigServiceImpl: logs when the Remote Configuration source starts and stops, and every document it receives or sees removed (config key and size, never the content). The log comes after the subscribers are notified, so it can never get in the way of a delivery.Tests in
RemoteConfigServiceImplTestcover the lifecycle and document logs, and check with a subscriber that a document is logged only after it is delivered.Motivation
Onboarding diagnostics for feature flags (FFL-3401), following the SDK logging checklist.
Since #12844 the agent only forwards the raw Remote Configuration documents and the
dd-openfeatureSDK parses and evaluates them, so the agent-side logging is small. The matching SDK diagnostics are in the stacked PR that targets this branch.Additional Notes
feature-flagging-libandfeature-flagging-agenttests and Spotless pass.Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issueJira ticket: FFL-3401
🤖 Generated with Claude Code