-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[jaeger-v2] Add Meter Provider To Telemetry Settings #6127
Closed
2 tasks
Labels
area/otel
enhancement
good first issue
Good for beginners
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
v2
Comments
mahadzaryab1
added
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
good first issue
Good for beginners
labels
Oct 26, 2024
4 tasks
4 tasks
Hi @mahadzaryab1 we should be adding |
@akstron yes that’s correct! |
4 tasks
4 tasks
Still see two more places in non-test code
|
@yurishkuro Those are in the context of v1 - can we do anything there? |
Fair enough, we can close this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/otel
enhancement
good first issue
Good for beginners
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
v2
Requirement
We're currently using no-op meter providers in the code instead of propagating the provider from OTEL. To change this, we need to do the following:
noopmetric.NewMeterProvider()
is usedThe text was updated successfully, but these errors were encountered: