Conversation
This comment has been minimized.
This comment has been minimized.
Binary Size Analysis (Agent Data Plane)Baseline: 08cd4c4 · Comparison: 9394c95 · diff ✅ Binary size difference within thresholdChanges by Module
Detailed Symbol Changes |
Regression Detector (Agent Data Plane)Run ID: Optimization Goals: ✅ No significant changes detectedFine details of change detection per experiment (35)Experiments configured
Bounds Checks: ✅ Passed (5)
ExplanationA change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression ( |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 086d64325b
ℹ️ 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".
… MRF from sending to primary endpoint twice
| endpoint.set_dd_url(dd_url); | ||
| endpoint.set_api_key(api_key); | ||
| self.forwarder_config.clear_opw_metrics_endpoint(); | ||
| self.configuration = None; |
There was a problem hiding this comment.
Is multi_region_failover.api_key refreshed anywhere at all? with_endpoint_override() drops the live config reference, so this looks static even if the config stream later updates the MRF API key.
There was a problem hiding this comment.
To my understanding, I don't think that the API Key should be updated dynamically based on the following snippet from the Core Agent (https://github.com/DataDog/datadog-agent/blob/ec7bc68731a4e3561a4c5f5366a46c24b9e28368/cmd/agent/subcommands/run/command.go#L556-L573) which lists the config vars that could be changed at runtime.
I could be wrong though. So feel free to clarify.
Summary
Parses six config keys (
multi_region_failover.enabled,multi_region_failover.failover_metrics,multi_region_failover.metric_allowlist,multi_region_failover.api_key,multi_region_failover.site,multi_region_failover.dd_url) to build multi-region failover configuration.Creates a new transform that ingests the configuration to determine what endpoint to send data to as a failover, and which metrics to forward (if a
metric_allowlistis configured).The architecture also opens the possibility to expand capabilities to logs and traces in a way that is compliant with existing ADP patterns.
Change Type
How did you test this PR?
Unit tests.
References
multi_region_failover.*config keys. #1678