-
Notifications
You must be signed in to change notification settings - Fork 0
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
Support OTEL_SERVICE_NAME #425
Comments
Thank you for your feature request! This is a good suggestion, and we appreciate you bringing it to our attention. Temporal currently uses the service name from the Temporal Server, but your suggested approach using the For now, a possible workaround is to use a convention for naming services within your organization. For example, you could prefix service names with the team name or the cluster name. This would help to distinguish services from different teams or clusters even though they are all using the same Temporal Server. We are looking into implementing your suggested feature, and we'll keep you updated on our progress. |
Thank you for your feature request. Currently, there isn't a way to directly set a custom For example, if you set
You can find more information about the |
Is your feature request related to a problem? Please describe.
No way to set a custom service.name in the trace. If several teams in an orgs spawn and manage their own cluster, they all appear under the same service name.
It would be pretty useful to customize the service.name, by allowing to set a prefix for example?
Describe the solution you'd like
Use OTEL_SERVICE_NAME env var to customize the service.name in the trace.
If OTEL_SERVICE_NAME is set:
else:
Describe alternatives you've considered
None
The text was updated successfully, but these errors were encountered: