Problem
The core agent includes an experimental HTTP/H2C-based DogStatsD ingestion frontend controlled by:
dogstatsd_experimental_http.enabled — toggles the experimental HTTP listenerdogstatsd_experimental_http.listen_address — bind address for the HTTP listener
ADP does not implement this transport. It is currently classified as not-applicable, but this needs formal confirmation and a documented decision.
What needs to happen
Determine the intended customer use case for the experimental HTTP DogStatsD listener (e.g. clients that cannot use UDP or UDS). Decide whether ADP should implement an equivalent HTTP ingestion path, defer it, or explicitly document it as out of scope. If out of scope, add a clear reason to the Not Planned section of the configuration docs.
Problem
The core agent includes an experimental HTTP/H2C-based DogStatsD ingestion frontend controlled by:
dogstatsd_experimental_http.enabled— toggles the experimental HTTP listenerdogstatsd_experimental_http.listen_address— bind address for the HTTP listenerADP does not implement this transport. It is currently classified as not-applicable, but this needs formal confirmation and a documented decision.
What needs to happen
Determine the intended customer use case for the experimental HTTP DogStatsD listener (e.g. clients that cannot use UDP or UDS). Decide whether ADP should implement an equivalent HTTP ingestion path, defer it, or explicitly document it as out of scope. If out of scope, add a clear reason to the Not Planned section of the configuration docs.