An error was encountered in jaeger ui.

[xucq07]

As shown in the figure

Version jaeger 1.57.0

Describe:

I used the jaeger-clickhouse plugin to use clickhouse as the backend storage. The specific deployment method is to add kafka as a buffer between jaeger-collector and jaeger-ingester. However, I cannot solve the error reported by jaeger ui.

The error log is as follows

{"level":"error","ts":1727862353.8691428,"caller":"app/http_handler.go:504","msg":"HTTP handler, Internal Server Error","error":"plugin error: rpc error: code = Unknown desc = not implemented","stacktrace":"github.com/jaegertracing/jaeger/cmd/query/app.(*APIHandler).handleError\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/http_handler.go:504\ngithub.com/jaegertracing/jaeger/cmd/query/app.(*APIHandler).dependencies\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/http_handler.go:311\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2166\ngithub.com/jaegertracing/jaeger/cmd/query/app.(*APIHandler).handleFunc.traceResponseHandler.func2\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/http_handler.go:548\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2166\ngo.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.WithRouteTag.func1\n\tgo.opentelemetry.io/contrib/instrumentation/net/http/[email protected]/handler.go:249\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2166\ngo.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*middleware).serveHTTP\n\tgo.opentelemetry.io/contrib/instrumentation/net/http/[email protected]/handler.go:212\ngo.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.NewMiddleware.func1.1\n\tgo.opentelemetry.io/contrib/instrumentation/net/http/[email protected]/handler.go:73\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2166\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2166\ngithub.com/gorilla/mux.(*Router).ServeHTTP\n\tgithub.com/gorilla/[email protected]/mux.go:212\ngithub.com/jaegertracing/jaeger/cmd/query/app.createHTTPServer.additionalHeadersHandler.func4\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/additional_headers_handler.go:28\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2166\ngithub.com/jaegertracing/jaeger/cmd/query/app.createHTTPServer.CompressHandler.CompressHandlerLevel.func6\n\tgithub.com/gorilla/[email protected]/compress.go:141\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2166\ngithub.com/gorilla/handlers.recoveryHandler.ServeHTTP\n\tgithub.com/gorilla/[email protected]/recovery.go:78\nnet/http.serverHandler.ServeHTTP\n\tnet/http/server.go:3137\nnet/http.(*conn).serve\n\tnet/http/server.go:2039"}

[dosubot[bot]]

Hello, @xucq07! I'm here to help you with your Jaeger UI error. I'm a bot that can assist with bug-solving, answering questions, and becoming a contributor.

The error message "plugin error: rpc error: code = Unknown desc = not implemented" indicates that the jaeger-clickhouse plugin does not support the /api/dependencies endpoint. This endpoint is used to retrieve the service dependencies graph, and if the plugin does not implement this functionality, it will result in the error you are seeing.

To resolve this issue, you can:

1. Verify Plugin Support: Check if the version of the jaeger-clickhouse plugin you are using supports the /api/dependencies endpoint. If not, you may need to look for an alternative solution or plugin that supports this feature.

2. Alternative Approaches: If the plugin does not support this endpoint, consider using a different storage backend that does, or implement the required functionality in the plugin if possible.

3. Check for Updates: Ensure that you are using the latest version of the jaeger-clickhouse plugin, as newer versions might have added support for this endpoint.

Unfortunately, I couldn't find specific information on whether the jaeger-clickhouse plugin supports this endpoint or any additional configuration required for it ^[1].

To continue talking to Dosu, mention @dosu.

[yurishkuro]

The bot is partially correct. The backend does not implement dependencies api in grpc service (not in the http endpoint which is handled by jaeger itself).