OpenTelemetry Metrics Support for Live Metrics #3792
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
merge conflict
navsukumar
requested review from
heyams,
jeanbisutti,
ramthi,
trask and
harsimar
as code owners
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.
Do not approve yet, will be making updates to sdk and will have to update the exporter jar files accordingly.
Summary: This PR is linked to the changes proposed in this PR . This PR introduces using a separate Metric Reader to retrieve open telemetry metrics.
SecondEntryPoint: Modified such that a QuickPulseMetricReader instance, whose class is defined in the linked PR, gets instantiated and passed into a QuickPulse instance. This enables the QuickPulse instance to retrieve and export Open Telemetry metrics at any given time.