Skip to content

Allow configuration of jaeger client in the query service #1044

@black-adder

Description

@black-adder

Requirement - what kind of business use case are you trying to solve?

The jaeger query service allows for tracing the query service itself. In the all-in-one container, the default initialization of the client works since the agent/collector reside on localhost. However, when the query service is deployed individually, the collector and agent are not guaranteed to be running locally or maybe running on non-default ports depending on the setup.

Problem - what in Jaeger blocks you from solving the requirement?

The query service exposes no flags or environment variables to configure the tracer in the query service.

Proposal - what do you suggest to solve the problem or improve the existing situation?

The golang tracer allows configuration via environment variables. I think all we'd have to do is to replace New with FromEnv.

Any open questions to address

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementgood first issueGood for beginnershelp wantedFeatures that maintainers are willing to accept but do not have cycles to implement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions