Add support for disabling DogStatsD payloads from being forwarded. #387
Labels
area/components
Sources, transforms, and destinations.
area/config
Configuration.
effort/intermediate
Involves changes that can be worked on by non-experts but might require guidance.
source/dogstatsd
DogStatsD source.
type/enhancement
An enhancement in functionality or support.
Context
In the Datadog Agent, the forwarding of specific types of payloads -- events, service checks, series, sketches, and more -- can be disabled through the configuration, as seen here.
This is, in generally, extremely niche, but we'll want to make sure we support it.
Notes
The Datadog Agent handles this in the flush/serialization phase, but we should figure out if there's any good reason to even bother creating the events and shuffling them through the topology, since it would be vastly more efficient to just drop them before sending them out of the DogStatsD source.
The text was updated successfully, but these errors were encountered: