New APIs to add/remove metric readers at run-time#4863
New APIs to add/remove metric readers at run-time#4863JP-MY wants to merge 1 commit intoopen-telemetry:mainfrom
Conversation
|
|
aabmass
left a comment
There was a problem hiding this comment.
Thanks for the PR, sorry for the delay here.
ef20f0e to
9bb1567
Compare
|
@aabmass @herin049 I'm not sure why the lint is failing for protected access, I can see the same protected access in the same file. Should I add a |
aabmass
left a comment
There was a problem hiding this comment.
Thanks for fixing the concurrency issues, LGTM!
| ) | ||
| return self._meters[info] | ||
|
|
||
| def add_metric_reader( |
There was a problem hiding this comment.
Can we start with private methods and see if the declarative config work has any interaction with this?
There was a problem hiding this comment.
I'm not familiar with the declerative config work but we need this API accessible at run time (after initial configuration). Would that be supported by the decelartive config work?
There was a problem hiding this comment.
I have addressed all other comments, if we are ok with the public API can we proceed with merging this?
8a5c6ef to
04a652a
Compare
| ) | ||
| return self._meters[info] | ||
|
|
||
| def add_metric_reader( |
There was a problem hiding this comment.
Can we start with private methods and see if the declarative config work has any interaction with this?
Description
This change adds two public functions to MeterProvider that allow registering and deleting metric readers at run-time.
Fixes #4818
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Does This PR Require a Contrib Repo Change?
Checklist: