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}

[dosubot[bot]]

The error message indicates that the HotROD application is trying to send traces to the Jaeger Collector using the OpenTelemetry HTTP port 4318, but the connection is being refused. Here are a few steps to troubleshoot and resolve this issue:

1. Verify Collector Configuration: Ensure that the Jaeger Collector is configured to listen on port 4318 for OpenTelemetry HTTP traffic. This can be set in the configuration file used by Jaeger.

2. Check Network Connectivity: Make sure that the IP address 192.168.121.73 is correct and that the Jaeger Collector is running on this host. Verify that there are no network issues or firewall rules blocking the connection to port 4318.

3. Port Exposure: Confirm that port 4318 is exposed and mapped correctly in your Docker Compose file. The ports section should include 4318:4318 to ensure that the port is accessible from outside the container.

4. Collector Logs: Check the logs of the Jaeger Collector to see if there are any errors or warnings related to the OpenTelemetry HTTP receiver. This might provide additional insights into why the connection is being refused.

5. Configuration File: Ensure that the configuration file used by Jaeger includes the necessary settings to enable the OpenTelemetry HTTP receiver on port 4318. The configuration should specify the receiver and its associated port.

By following these steps, you should be able to identify and resolve the issue with the HotROD application connecting to the Jaeger Collector.

To continue talking to Dosu, mention @dosu.

---

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

[yogesh119905]

@dosu, I have fixed that issue, just adding endpoint 0.0.0.0:4318 in receivers section in collector configuration. now network is enabled, But still I am getting when I generate traces on hotrod app and jaeger query is unable to fetched that traces, I found error at hotrod application "2025-01-26T04:31:4 ERROR driver/redis.go:70 redis timeout {"service": "driver", "trace_id": "63e7d3f10a69eb896daa5c70356b2062", "span_id": "d262494aae5bad9c", "driver_id": "T777791C", "error": "redis timeout"}
2025-01-26T04:31:49.940Z ERROR driver/server.go:74 Retrying GetDriver after error {"service": "driver", "trace_id": "63e7d3f10a69eb896daa5c70356b2062", "span_id": "a00c8557f2482c26", "retry_no": 1, "error": "redis timeout"}". Is there any thing do I need to configuration ? Below is my jaeger configuration setup/

[dosubot[bot]]

The "redis timeout" error you're encountering in the HotROD application is likely due to simulated delays and error conditions within the Redis simulator used in the application. This is a known behavior in the HotROD example, where the errorSimulator struct is designed to introduce a timeout error after a certain number of successful operations. This is done to simulate network latency and timeout conditions that might occur in a real Redis environment ^[1].

To address this, you can:

1. Review the HotROD Code: Check the GetDriver method in the HotROD application's code to understand how the errorSimulator is configured. You might want to adjust the delay or error simulation settings if you want to reduce the frequency of these simulated timeouts.

2. Configuration Adjustments: If you have access to the configuration settings for the Redis simulator, you can modify the delay and error simulation parameters to better suit your testing needs.

3. Testing Environment: Ensure that your testing environment is set up to handle these simulated conditions, or consider disabling the error simulation if it's not needed for your current testing purposes.

These steps should help you manage the "redis timeout" errors in the HotROD application.

To continue talking to Dosu, mention @dosu.

---

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

[yogesh119905]

@dosu, Okay, after generating an traces, I am unable to receive that trace in jaeger query api. What is the problem in configuration file. I have attached config file and comose file. Cab you please reviewd it?

[dosubot[bot]]

To troubleshoot the issue of not receiving traces in the Jaeger query API, here are some key areas to review in your configuration and Docker Compose setup:

1. Storage Configuration: Ensure that the Elasticsearch configuration in your Jaeger setup is correct. Verify that the es.server-urls in your configuration file points to the correct Elasticsearch server URL(s). Also, check that the indices and other Elasticsearch-related settings are properly configured ^[1].

2. Collector and Query Configuration: Make sure that the Jaeger Collector is correctly configured to receive and process traces. The Collector should be able to communicate with Elasticsearch to store the traces. Similarly, the Jaeger Query component should be configured to retrieve traces from Elasticsearch. Ensure that both components are using the correct configuration file paths and settings.

3. Network and Connectivity: Verify that there are no network issues preventing the Jaeger components from communicating with each other and with Elasticsearch. Check that the ports specified in your Docker Compose file are correctly exposed and mapped.

4. Logs and Errors: Check the logs of both the Jaeger Collector and Query components for any errors or warnings that might indicate issues with trace processing or retrieval. This can provide insights into what might be going wrong.

5. Configuration File: Ensure that the configuration file used by Jaeger is correctly formatted and includes all necessary settings for your environment. Double-check the paths and values for any critical parameters, such as storage backend settings and endpoint configurations.

By reviewing these areas, you should be able to identify and resolve the issue preventing traces from being received by the Jaeger query API.

To continue talking to Dosu, mention @dosu.

---

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