-
Notifications
You must be signed in to change notification settings - Fork 652
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
Exporters shouldn't have service name parameter #1607
Comments
@lonewolf3739 , pls assign this to me |
@dmarar I don't have permissions to assign. @lzchen / @codeboten can assign this to you. |
@dmarar assigned! thanks |
@lonewolf3739 , Just to clarify on the requirement:
|
@dmarar it would look something like this from opentelemetry import trace
from opentelemetry.sdk.resources import SERVICE_NAME
tracer_provider = trace.get_tracer_provider()
resource = tracer_provider.resource
svc_name = resource.attributes[SERVICE_NAME] |
Should we remove |
Yes, that's what I mentioned in the issue title, I hope that's conveying the same? We need to remove the service_name param and use the Resource attribute. |
@lonewolf3739 - I have created a draft PR 1669 I did not find any other place where the service_name is being used in exporters. Thanks, |
This was fixed by #1669 |
Exporters
jaeger
,zipkin
andopencensus
accept an argumentservice_name
but ideally they should rely on theResource
'sservice.name
attribute from Tracer/Span to indicate the resource that produced the corresponding telemetry.The text was updated successfully, but these errors were encountered: