We currently support the more basic/generalized origin detection mechanisms, such as utilizing the peer process ID on the other end of a UDS-based DogStatsD client, or the "container ID" DogStatsD extension, or the dd.internal.entity_id tag.
However, we lack support for the newly-added "External Data" origin detection, which uses a stringified list of data attributes, passed in a new DogStatsD field, to provide richer origin data than just container ID alone.
We should add support for this in order to ensure our origin detection support is at parity with the Datadog Agent.
Context
We currently support the more basic/generalized origin detection mechanisms, such as utilizing the peer process ID on the other end of a UDS-based DogStatsD client, or the "container ID" DogStatsD extension, or the
dd.internal.entity_idtag.However, we lack support for the newly-added "External Data" origin detection, which uses a stringified list of data attributes, passed in a new DogStatsD field, to provide richer origin data than just container ID alone.
We should add support for this in order to ensure our origin detection support is at parity with the Datadog Agent.