feat(influx2otel): add influx->otel package #1
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
|
I'd love to see this merged as I could make use of it right away in influxdata/telegraf#9109. The surface area of the API seems right to me. Based on the data types supported in the line protocol, using gauges seems like a good starting point. |
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.
Package influx2otel converts line protocol tuples into OpenTelemetry Metrics protocol buffer objects.
Line protocol has a much simpler schema compared to OpenTelemetry. As such, it is not possible to reliably guess metric types based on line protocol alone. Therefore, this proposal simply treats everything like a gauge.