Jaeger v2 docker image configuration

[vvuk]

I could just be missing it, but I can't find anywhere in the documentation about how to actually provide a configuration file to the jaeger v2 docker container. (The docs don't even seem to give information where the config file lives or is passed in.)

This is me trying to set QUERY_BASE_PATH (which doesn't seem to work via env var any more?). Any suggestions?

[dosubot[bot]]

Hey @vvuk 👋, I'm here to assist you with any bugs, questions, or contributions you have. Let's tackle this together!

To provide a configuration file to the Jaeger v2 Docker container and set QUERY_BASE_PATH, you need to mount a configuration file into the container. The default location for configuration files in the Jaeger v2 Docker container is /etc/jaeger/ ^[1].

Here's how you can modify your Docker Compose file to include a volume that mounts your configuration file into the container:

services:
  jaeger:
    image: docker-release.repo.XXX.cz/jaegertracing/jaeger:2.0.0
    container_name: jaeger
    hostname: jaeger  
    ports: ['14268:14268', '14269:14269', '14250:14250', '4318:4318', '4317:4317', '16686:16686', '16687:16687', '16685:16685']
    restart: 'unless-stopped'
    environment:
      SPAN_STORAGE_TYPE: 'elasticsearch'
    volumes:
      - '/var/opt/jaeger:/var/opt/jaeger'
      - './jaeger-config.yaml:/etc/jaeger/jaeger-config.yaml'  # Mount your config file

Ensure that your jaeger-config.yaml file is correctly formatted and includes the necessary configuration for query.base-path. You can specify the query.base-path option in your configuration file like this:

query:
  base-path: /your/base/path

This setup should allow you to configure the QUERY_BASE_PATH using a configuration file. For more details on the configuration file format and options, you can refer to Jaeger's official documentation ^[2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[vvuk]

ah ha. thanks!

[yurishkuro]

Added example to the docs jaegertracing/documentation#835

[vvuk]

Ok -- so I think more examples are needed here: https://www.jaegertracing.io/docs/2.2/configuration/ This page references the otel collector configuration and says "The configuration defines the main ingestion pipeline as a collection of receivers, processors, connectors, and exporters." and then defines some of the jaeger extensions. But there's no example of such a config file that configures one of the jaeger extensions.

Ideally with:

1. An actual complete simple config file, i.e. something I can pass to --config and have things work.
2. The default "all in one" config file (because I think passing --config will override that?)

[vvuk]

Or is this the default config file?

[yurishkuro]

it's not a "default" config, it's an example of a config. The same dir has many other config examples for different storage types.