-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[service] remove code to configure otel SDK #9131
[service] remove code to configure otel SDK #9131
Conversation
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
14e2eb7
to
f8f0592
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #9131 +/- ##
==========================================
- Coverage 90.34% 90.34% -0.01%
==========================================
Files 340 340
Lines 17989 17873 -116
==========================================
- Hits 16253 16148 -105
+ Misses 1412 1404 -8
+ Partials 324 321 -3 ☔ View full report in Codecov by Sentry. |
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.
Should we wait for the next config
release?
I don't have a strong preference here, happy to go either ways |
This code will live in the otel-go-contrib `config` package instead. This PR depends on open-telemetry/opentelemetry-go-contrib#4617 Signed-off-by: Alex Boten <aboten@lightstep.com>
Signed-off-by: Alex Boten <aboten@lightstep.com>
Signed-off-by: Alex Boten <aboten@lightstep.com>
3c5ef94
to
34f586a
Compare
They may have to do a release anyway for the gRPC issue, so I would hold on merging this for a bit to see if we get a release for this module as well. |
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.
LGTM, I merged main and bumped to v0.2.0 which has the changes we need for this
@@ -75,13 +74,20 @@ func (tel *telemetryInitializer) init(res *resource.Resource, settings servicete | |||
} | |||
|
|||
settings.Logger.Info("Setting up own telemetry...") | |||
configuredSDK, err := config.NewSDK( |
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.
One question: are we not passing the resource anymore here?
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.
This is a good question. I'm working on an issue in the go-contrib repo where setting resource attributes via config is currently restricted to service name, as the go-jsonschema library doesn't have support for additionalProperties on an object that has other properties specified.
Putting this back into draft until that's resolved (open-telemetry/opentelemetry-go-contrib#4828)
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.
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.
👍 Makes sense, let's wait on that issue to be solved then :)
Signed-off-by: Alex Boten <aboten@lightstep.com>
A part of open-telemetry#9319 that can be done without waiting for open-telemetry#9131
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
This code will live in the otel-go-contrib
config
package instead. This PR depends on open-telemetry/opentelemetry-go-contrib#4617Leaving this as draft until config package is updated. Ideally I'd like to get the MeterProvider configured in this PR as wellAddressing only TracerProvider in this initial PR.