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

Jaeger exporter should honor environment variables #792

Closed
Aneurysm9 opened this issue Jun 2, 2020 · 1 comment · Fixed by #796
Closed

Jaeger exporter should honor environment variables #792

Aneurysm9 opened this issue Jun 2, 2020 · 1 comment · Fixed by #796
Assignees
@XSAM
Labels
area:trace Part of OpenTelemetry tracing good first issue Good for newcomers
Milestone
Next

Comments

@Aneurysm9
Copy link
Member

The Jaeger exporter should utilize the standard environment variables used by other Jaeger clients to the extent that they make sense. At a minimum that is probably the following:

  • JAEGER_ENDPOINT
  • JAEGER_USER
  • JAEGER_PASSWORD
  • JAEGER_TAGS
  • JAEGER_DISABLED
@Aneurysm9 Aneurysm9 added good first issue Good for newcomers exporters area:trace Part of OpenTelemetry tracing labels Jun 2, 2020
@Aneurysm9 Aneurysm9 added this to the Next milestone Jun 2, 2020
@XSAM
Copy link
Member

XSAM commented Jun 4, 2020

@Aneurysm9 I'd like to take this up.

@XSAM XSAM mentioned this issue Jun 5, 2020
Merged
@XSAM XSAM mentioned this issue Aug 1, 2020
Closed
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@XSAM XSAM

Labels
area:trace Part of OpenTelemetry tracing good first issue Good for newcomers
Projects
None yet
Milestone
Next
Development

Successfully merging a pull request may close this issue.

Add environment variables for Jaeger exporter XSAM/opentelemetry-go
2 participants
@Aneurysm9 @XSAM