Support InfluxDB >= 0.11 with tags #36
Open
Conversation
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
|
Hi mchesler, bernd have stoped the update. Can your forked branch support the InfluxDB 0.13 version?? |
|
Hi @wangdiwen, yes, I'm using this branch with InfluxDB 0.13 and it's working great. |
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.
Per https://docs.influxdata.com/influxdb/v0.13/concepts/schema_and_data_layout/, it's better for InfluxDB to differentiate data with tags than with detailed measurement names. Tags are indexed and InfluxDB does not allow merging data across measurements, so parsing and tagging as built in this PR provides the best balance of flexibility and performance with InfuxDB. This change splits metrics like
appname.datacenter.hostname.requests:1|cinto:This has been tested against InfluxDB v0.13 in a high-volume production environment.