-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to view request page for flow functions #33
Comments
Are you running any open tracing agent ? Is your jaeger-agent is running/ |
I am facing a similar issue with But when I try to click the I have mentioned my setup in detail in #47. I have mentioned When I check the logs of 2023/10/13 08:36:23 stderr: 2023/10/13 08:36:23 Serving request for request list view
2023/10/13 08:36:23 GET /flow/requests?flow-name=sync-chain - 200 OK - ContentLength: -1B (0.0168s) I have the open tracing agent $ kubectl get pods --namespace faasflow
NAME READY STATUS RESTARTS AGE
consul-0 1/1 Running 0 18h
jaeger-7557db4c5d-74l46 1/1 Running 0 18h
minio-7f48b8fd-vwjxd 1/1 Running 0 18h Logs of the same: $ kubectl logs jaeger-7557db4c5d-74l46 --namespace faasflow
2023/10/12 14:09:26 maxprocs: Leaving GOMAXPROCS=12: CPU quota undefined
{"level":"info","ts":1697119766.341727,"caller":"flags/service.go:115","msg":"Mounting metrics handler on admin server","route":"/metrics"}
{"level":"info","ts":1697119766.3419302,"caller":"flags/admin.go:108","msg":"Mounting health check on admin server","route":"/"}
{"level":"info","ts":1697119766.3419874,"caller":"flags/admin.go:114","msg":"Starting admin HTTP server","http-port":14269}
{"level":"info","ts":1697119766.3420022,"caller":"flags/admin.go:100","msg":"Admin server started","http-port":14269,"health-status":"unavailable"}
{"level":"info","ts":1697119766.3452811,"caller":"memory/factory.go:56","msg":"Memory storage initialized","configuration":{"MaxTraces":0}}
{"level":"info","ts":1697119766.3529189,"caller":"all-in-one/main.go:246","msg":"Starting jaeger-collector TChannel server","port":14267}
{"level":"warn","ts":1697119766.352941,"caller":"all-in-one/main.go:247","msg":"TChannel has been deprecated and will be removed in a future release"}
{"level":"info","ts":1697119766.3532465,"caller":"grpcserver/grpc_server.go:64","msg":"Starting jaeger-collector gRPC server","grpc-port":"14250"}
{"level":"info","ts":1697119766.353351,"caller":"all-in-one/main.go:265","msg":"Starting jaeger-collector HTTP server","http-port":14268}
{"level":"info","ts":1697119766.353376,"caller":"grpc/builder.go:65","msg":"Agent requested insecure grpc connection to collector(s)"}
{"level":"info","ts":1697119766.354038,"caller":"all-in-one/main.go:203","msg":"Starting agent"}
{"level":"info","ts":1697119766.354078,"caller":"querysvc/query_service.go:133","msg":"Archive storage not created","reason":"archive storage not supported"}
{"level":"info","ts":1697119766.3540897,"caller":"all-in-one/main.go:347","msg":"Archive storage not initialized"}
{"level":"info","ts":1697119766.3540914,"caller":"app/agent.go:69","msg":"Starting jaeger-agent HTTP server","http-port":5778}
{"level":"info","ts":1697119766.35451,"caller":"healthcheck/handler.go:128","msg":"Health Check state change","status":"ready"}
{"level":"info","ts":1697119766.3545184,"caller":"app/server.go:112","msg":"Starting HTTP server","port":16686}
{"level":"info","ts":1697119766.3545265,"caller":"app/server.go:125","msg":"Starting GRPC server","port":16686}
{"level":"info","ts":1697119766.3545468,"caller":"app/server.go:135","msg":"Starting CMUX server","port":16686}
{"level":"info","ts":1697119766.3713021,"caller":"all-in-one/main.go:303","msg":"Listening for Zipkin HTTP traffic","zipkin.http-port":9411}
I do not think that the tracing agent is able to record anything. Any suggestions, like what might be going wrong? |
I was able to get faas-flow-tower installed and can view the dashboard, but I'm unable to see the request page. Each time I click on the requests link from the function I get the page stating I need to enable tracing. I've enable tracing with jaeger and used the internal ports along with the node ports for kubernetes but I'm still not having any luck.
When I try clicking on the link, I am getting an error in the faas-flow-dashboard container logs which is listed below
The text was updated successfully, but these errors were encountered: