Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Tracing requests: propagation and service name setting. #426

Closed
vasconcelosvcd opened this issue Sep 18, 2023 · 0 comments · Fixed by #427
Closed

Tracing requests: propagation and service name setting. #426

vasconcelosvcd opened this issue Sep 18, 2023 · 0 comments · Fixed by #427

Comments

@vasconcelosvcd
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
When using tracing in opensaves would be good to have two new features

  • Enable tracing propagation
  • Being able to set the name via opentelemetry env vars.

Additional context

  • When using tracing in opensaves as a service the tracing are not being propagated causing it not to have a full spans context.
  • At the moment the service name is set via attribute param and this is causing it to overwrite the open telemetry env var OTEL_SERVICE_NAME
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: tracing propagation and service name prioritize envvar vasconcelosvcd/open-saves
1 participant
@vasconcelosvcd