Closed chahatsagarmain closed 5 days ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 96.49%. Comparing base (
47e1ee6
) to head (1245dce
). Report is 1 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@mahadzaryab1 how will i propogate leveledmeterprovider where telset
is not part of function arguement ? Do i just use noop meterprovider there ?
@mahadzaryab1 how will i propogate leveledmeterprovider where
telset
is not part of function arguement ? Do i just use noop meterprovider there ?
Yes, it will not be available in the context of v1 so a noop provider can be used there.
I don't think this is addressing all places
$ rg otel/metric/noop
cmd/query/app/server.go
22: "go.opentelemetry.io/otel/metric/noop"
plugin/storage/grpc/factory.go
21: noopmetric "go.opentelemetry.io/otel/metric/noop"
cmd/collector/app/handler/otlp_receiver.go
24: noopmetric "go.opentelemetry.io/otel/metric/noop"
cmd/collector/app/handler/zipkin_receiver.go
16: noopmetric "go.opentelemetry.io/otel/metric/noop"
@yurishkuro (1) looks to be addressed in this PR. (3) and (4) are v1 components so we're passing in noop (https://github.com/jaegertracing/jaeger/blob/main/cmd/collector/app/handler/otlp_receiver.go#L71-L81). Is there anything else we can do for that?
@chahatsagarmain for (2) We can pass the meter provider down from this constructor and into the grpc factory.
@yurishkuro spm test is failing for recent prs
@yurishkuro spm test is failing for recent prs
Opened a PR for the fix: https://github.com/jaegertracing/jaeger/pull/6217
Thanks
Which problem is this PR solving?
How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:yarn lint
andyarn test