Conversation
Tags host and device are converted into metric attributes
Member
|
If we're going forward with this for 5.1, could you add an entry to changelog please? |
Contributor
Author
|
Sorry I forgot it, done here: d44f413 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, If someone report a
hostordevicetag with DogStatsD, the tag will conflict with thehostanddeviceattribute in the webapp. To avoid this confusion (and to allow not to set these optional fields with dogstatsd), this PR brings:host:fooanddevice:bartags will override the attributeshostname:fooanddevice_name:barhost:ordevice:), these fields are removed. Useful to remove the cardinality of metrics when they aren't useful.