feat: Open Telemetry target #30
Open
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
joshwestbrook
force-pushed
the
open-telemetry
branch
2 times, most recently
from
a9bb678 to
7008f29
Compare
joshwestbrook
force-pushed
the
open-telemetry
branch
from
7008f29 to
201635d
Compare
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.
Add support for an Open Telemetry target as an alternative to DataDog.
Wasn't sure of the best way to make it so that consumers of this gem don't have to pull in both the
dogstatsd-rubyandopentelemetry-*gems in order to use one of the targets. Open to any suggestions! 😄Note: The OTel Ruby Metrics SDK is under active development, so there is one pending PR and a pending release for gauge support: