SE_ENABLE_TRACING=false is not required when starting the container anymore

[VietND96]

By default, SE_ENABLE_TRACING is true to align with CLI option config https://www.selenium.dev/documentation/grid/configuration/cli_options/#logging.
It is recommended that the user enable observability for tracing issues if having any. However, by default, it auto config the endpoint to a local OTLP localhost/[0:0:0:0:0:0:0:1]:4317 and raises the warning if that endpoint is unreachable. The error looks like

2024-11-28 19:44:44 14:14:44.430 ERROR [ThrottlingLogger.doLog] - Failed to export spans. The request could not be executed. Error message: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:4317
2024-11-28 19:44:44 java.net.ConnectException: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:4317
2024-11-28 19:44:44     at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.kt:297)
2024-11-28 19:44:44     at okhttp3.internal.connection.RealConnection.connect(RealConnection.kt:207)
2024-11-28 19:44:44     at okhttp3.internal.connection.ExchangeFinder.findConnection(ExchangeFinder.kt:226)
2024-11-28 19:44:44     at okhttp3.internal.connection.ExchangeFinder.findHealthyConnection(ExchangeFinder.kt:106)
2024-11-28 19:44:44     at okhttp3.internal.connection.ExchangeFinder.find(ExchangeFinder.kt:74)
2024-11-28 19:44:44     at okhttp3.internal.connection.RealCall.initExchange$okhttp(RealCall.kt:255)
2024-11-28 19:44:44     at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:32)
2024-11-28 19:44:44     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2024-11-28 19:44:44     at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
2024-11-28 19:44:44     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2024-11-28 19:44:44     at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
2024-11-28 19:44:44     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2024-11-28 19:44:44     at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
2024-11-28 19:44:44     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2024-11-28 19:44:44     at io.opentelemetry.exporter.sender.okhttp.internal.RetryInterceptor.intercept(RetryInterceptor.java:91)
2024-11-28 19:44:44     at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2024-11-28 19:44:44     at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
2024-11-28 19:44:44     at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
2024-11-28 19:44:44     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
2024-11-28 19:44:44     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
2024-11-28 19:44:44     at java.base/java.lang.Thread.run(Thread.java:840)
2024-11-28 19:44:44     Suppressed: java.net.ConnectException: Failed to connect to localhost/127.0.0.1:4317
2024-11-28 19:44:44             ... 21 more
2024-11-28 19:44:44     Caused by: java.net.ConnectException: Connection refused
2024-11-28 19:44:44             at java.base/sun.nio.ch.Net.pollConnect(Native Method)
2024-11-28 19:44:44             at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
2024-11-28 19:44:44             at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:547)
2024-11-28 19:44:44             at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602)
2024-11-28 19:44:44             at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
2024-11-28 19:44:44             at java.base/java.net.Socket.connect(Socket.java:633)
2024-11-28 19:44:44             at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:128)
2024-11-28 19:44:44             at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.kt:295)
2024-11-28 19:44:44             ... 20 more

This warning doesn't impact the Grid functions, but it might annoy users or cause messed up logs to identify another real issue.

Instead of repetitively asking the user to add env var SE_ENABLE_TRACING=false when starting the container or in the docker-compose file, so on.

We updated the condition to enable tracing feature to be SE_ENABLE_TRACING=true, and users must input a correct endpoint to env var SE_OTEL_EXPORTER_ENDPOINT (it is empty by default). Otherwise, tracing is disabled internally.

Affected image tag: 4.23.1-20240812+
Fixed image tag: 4.27.0-20250101