WIP: Use an internal 'Metric' data type for telegraf metrics #576
Conversation
This file contains 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
sparrc
changed the title
sparrc
force-pushed
the
internal-metric
branch
3 times, most recently
from
e3ecf4b
to
dc77c65
Compare
As of now, this is pretty much just a wrapper around client.Point, but this gives latitude to expand functionality more easily. closes #564
sparrc
force-pushed
the
internal-metric
branch
2 times, most recently
from
de5be1b
to
837fa9e
Compare
sparrc
force-pushed
the
internal-metric
branch
from
837fa9e
to
a86d98f
Compare
|
closing this, going to try a slightly different approach to solve renaming all the different |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As of now, this is pretty much just a wrapper around client.Point, but
this gives latitude to expand functionality more easily.
closes #564