linghengqian commented on issue #32793: URL: https://github.com/apache/shardingsphere/issues/32793#issuecomment-3718460454
Based on my tests at https://github.com/linghengqian/shardingsphere-elastic-apm-playground/commit/fb27b966e400c22f74912bb81c2406fe57e09326 , ShardingSphere Agent 5.5.2 can no longer connect to Elastic Agent 9.2.3, although it can connect to Jaeger 2.14.1 normally. This seems to warrant an additional issue to test a different testing workflow. However, the backpressure case for metrics does indeed need to be fixed. ```shell 2026-01-07T18:28:42.363+08:00 INFO 469468 --- [shardingsphere-smoke-tests] [omcat-handler-1] ShardingSphere-SQL : Logic SQL: SELECT * FROM t_order_item WHERE user_id = 2024 2026-01-07T18:28:42.364+08:00 INFO 469468 --- [shardingsphere-smoke-tests] [omcat-handler-1] ShardingSphere-SQL : Actual SQL: ds_0 ::: SELECT * FROM t_order_item WHERE user_id = 2024 2026-01-07T18:29:47.769+08:00 WARN 469468 --- [shardingsphere-smoke-tests] [alhost:4317/...] o.a.s.s.i.o.e.i.grpc.GrpcExporter : Failed to export metrics. Server responded with gRPC status code 2. Error message: Failed to connect to localhost/127.0.0.1:4317 2026-01-07T18:30:48.443+08:00 WARN 469468 --- [shardingsphere-smoke-tests] [alhost:4317/...] o.a.s.s.i.o.e.i.grpc.GrpcExporter : Failed to export metrics. Server responded with gRPC status code 2. Error message: Failed to connect to localhost/127.0.0.1:4317 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
