We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
我本地安装了Crane服务,通过调用外部的Prometheus进行获取节点数据状态,同时Prometheus也添加了对应的rule规则及对应的targets,单独访问Prometheus对PromSql进行插叙也可以查询到数据。 但是通过craned Dashbord访问状态的时候,F12中会有好多的请求处在Pending状态。 通过查看craned pod的log,提示如下: 2023/08/21 15:29:30 [Recovery] 2023/08/21 15:29:30 panic recovered: write tcp 10.16.34.139:8082 -> 10.105.81.124:58288: i/o timeout /go/pkg/mod/githu.com/gin-gonic/[email protected]/render/json.go:56 (0x1a1d604)
其中10.16.34.139是craned 的容器ip ,10.105.81.124是craned svc对应的ip
求指导。
The text was updated successfully, but these errors were encountered:
可能的思路是:exec到craned容器内访问prometheus测试下
Sorry, something went wrong.
No branches or pull requests
我本地安装了Crane服务,通过调用外部的Prometheus进行获取节点数据状态,同时Prometheus也添加了对应的rule规则及对应的targets,单独访问Prometheus对PromSql进行插叙也可以查询到数据。
但是通过craned Dashbord访问状态的时候,F12中会有好多的请求处在Pending状态。
通过查看craned pod的log,提示如下:
2023/08/21 15:29:30 [Recovery] 2023/08/21 15:29:30 panic recovered:
write tcp 10.16.34.139:8082 -> 10.105.81.124:58288: i/o timeout
/go/pkg/mod/githu.com/gin-gonic/[email protected]/render/json.go:56 (0x1a1d604)
其中10.16.34.139是craned 的容器ip ,10.105.81.124是craned svc对应的ip
求指导。
The text was updated successfully, but these errors were encountered: