Expose the entity id to allow using Datadog origin detection #58
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.
Expose
entityId
that is added as a tag and allow using Datadog origin detection.In the original implementation they are getting it from the
DD_ENTITY_ID
environment variable if not provided. I didn't do it in order to mimic thecontainerId
behavior, and this can be done in user code anyway.Because
DatadogEncoder
can't modify tags, I modifiedStatsdEncoder
to allow passing constant tags that are added to every metric event. Using aString
is more efficient than adding tags as it doesn't need to be formatted every time. The dogstatsd has a similar approach.