Module config 

Configuration model and rendering for Datadog Agent configuration.

Primary focus is currently DogStatsD but this is, hopefully, easy to expand in the future.

One datadog.yaml is sampled per timeline. Only keys ADP and the Datadog Agent both fully support are emitted, and their values vary per timeline, so a divergence between the two targets is a finding rather than a config artifact.

Structs

DatadogConfig

Agent-facing config. hostname, api_key, dd_url, and the socket are supplied by the environment; log_level and the DogStatsD options are sampled per branch. The static flags are appended by Self::to_yaml, not fields here.

DriverConfig

Config a load generator reads to shape its output to this timeline’s SUT. first_sample_config samples it beside datadog.yaml from one draw, so the generator and the SUT are driven together.