-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add local storage and retry logic for Azure Metrics Exporter + flush telemetry on exit #845
Merged
Merged
Changes from 5 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
167fc5d
Refactor Options in metrics exporter constructor
lzchen 44b2187
Implement local storage and retry logic
lzchen 677aa84
Merge branch 'master' of https://github.com/census-instrumentation/op…
lzchen 7e232ca
fix tests
lzchen 811971b
Fix Lint
lzchen 202787d
FLush telemetry
lzchen 7463d5a
ADdress feedback
lzchen fa88dca
Merge branch 'master' of https://github.com/census-instrumentation/op…
lzchen e970b2a
fix lint
lzchen fea27da
fix lint
lzchen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MetricsExporter
isn't aBaseExporter
because we're using the export thread fromget_exporter_thread
instead ofBaseExporter
's worker?It looks like there's a fair amount of duplicated code here, and that
BaseExporter
should be refactored or made specific to tracing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it seems like
MetricsExporter
andAzureLogHandler
have very similar behaviour in terms of the exporter thread. I would like to eventually have all of them be aBaseExporter
. Was there any discussions with you and Reiley why this shouldn't be the case (why it was like this in the first place)? In any case, I'd like to keep those refactoring changes separate from a feature PR like this one, but I will cut a ticket open for it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[#852]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like
BaseExporter
was factored out in #642, but that PR didn't touch theStackdriverStatsExporter
, which influenced the design of the other stats exporters. In any case this can be a problem for another PR.