How to migrate jaeger v1.63.00 to v2.0.0

[yogesh119905]

Hello all, I have planned to upgrade Jaeger from version 1.63.0 to 2.0.0. In my current environment, I have separated the Jaeger query and collector components with their own Docker Compose files. How should I handle the migration to version 2.0.0?

[dosubot[bot]]

Hey @yogesh119905! 👋 I'm here to help you with any bugs, questions, or contributions you have while we wait for a human maintainer.

When upgrading Jaeger from version 1.63.0 to 2.0.0, there are several important changes and deprecations to consider, especially for the query and collector components:

1. Configuration Changes:

   • For the Query Server, the flags --query.port and --query.host-port have been removed. Use --query.http-server.host-port (defaults to :16686) and --query.grpc-server.host-port (defaults to :16685) instead.
   • For the Collector, replace --collector.http-port with --collector.http-server.host-port, --collector.grpc-port with --collector.grpc-server.host-port, and --collector.zipkin.http-port with --collector.zipkin.host-port ^[1].

2. TLS Configuration:

   • If TLS is enabled on either or both gRPC or HTTP endpoints, ensure that the gRPC and HTTP host-ports are different. If TLS is disabled, you can set a common host-port using the respective flags ^[1].

3. Docker Compose Files:

   • While specific changes to Docker Compose files weren't detailed, ensure that the updated flags and configurations are reflected in your Docker Compose setup. This includes updating the environment variables or command sections to use the new flags.

Make sure to test the updated configuration in a staging environment before deploying to production to ensure everything works as expected.

To continue talking to Dosu, mention @dosu.

---

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

[yogesh119905]

root@virt-jaeger:/var/opt/jaeger# cat /opt/jaeger/docker-compose.yml
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']
root@virt-jaeger:/var/opt/jaeger#
@dosu, Is the docker compose file content correct? if it is correct, still am I getting an below alert?
root@virt-jaeger:/var/opt/jaeger# docker logs -f jaeger
2025/01/16 10:14:04 application version: git-commit=3f752c2f434fabde20694816c264cfe8b546c575, git-version=v2.0.0, build-date=2024-11-10T18:53:12Z
Error: unknown flag: --config-file
2025/01/16 10:14:04 unknown flag: --config-file
2025/01/16 10:14:05 application version: git-commit=3f752c2f434fabde20694816c264cfe8b546c575, git-version=v2.0.0, build-date=2024-11-10T18:53:12Z
Error: unknown flag: --config-file
2025/01/16 10:14:05 unknown flag: --config-file
2025/01/16 10:14:06 application version: git-commit=3f752c2f434fabde20694816c264cfe8b546c575, git-version=v2.0.0, build-date=2024-11-10T18:53:12Z
Error: unknown flag: --config-file
2025/01/16 10:14:06 unknown flag: --config-file

[dosubot[bot]]

The error message "unknown flag: --config-file" suggests that the --config-file flag is not recognized by the Jaeger binary you are using. In Jaeger version 2.0.0, the --config-file flag is indeed used to specify a configuration file in various formats like JSON, TOML, YAML, HCL, or Java properties ^[1].

Here are a few things to check:

1. Binary Version: Ensure that the Jaeger binary you are using is indeed version 2.0.0. You can verify this by checking the image tag in your Docker Compose file, which should be jaeger:2.0.0.

2. Command Configuration: Check if the --config-file flag is being used correctly in your Docker Compose file or any startup scripts. Ensure that the path to the configuration file is correct and accessible within the container.

3. Image Source: Since you are using a custom Docker registry (docker-release.repo.XXX.cz), verify that the image is built correctly and includes the expected features of Jaeger 2.0.0. There might be a discrepancy if the image was custom-built or modified.

If the issue persists, consider testing with the official Jaeger image from Docker Hub to rule out any issues with the custom image.

To continue talking to Dosu, mention @dosu.

---

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

[yurishkuro]

The cli flags from v1 are not applicable to v2. V2 is only configured through config file.

[yogesh119905]

@yurishkuro, Yes you are correct it, but I never used in my docker compose file. is there any step by step migration document available? if you are suggesting looking for below document it will not helpful very much. kindly suggest any other document? https://www.jaegertracing.io/docs/2.0/migration/

[yurishkuro]

I don't understand what specifically you are asking.