enhancement: add a new DogStatsD-specific exporter #548
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
This PR adds a brand new exporter,
metrics-exporter-dogstatsd
, which is specifically designed for sending metrics using the DogStatsD protocol, typically to a Datadog Agent or DogStatsD server.While
metrics-exporter-statsd
exists and works well for many use cases, it depends oncadence
which ultimately limits the maximum performance and capabilities of any exporter depending on it. This shows up in terms of cached access to metrics and things like optimal payload building, and so on.Further, while libraries like
cadence
do strive to support DogStatsD-specific features, it doesn't aspire to (to my knowledge) match support with the official DogStatsD client libraries, whilemetrics-exporter-dogstatsd
does. This includes support for client-side aggregation, histogram sampling, smart reporting, and more.Notes
We've done some unrelated refactoring/cleanup in
metrics-util
to add the necessary bits for the new exporter.