deepflowio / deepflow

eBPF Observability - Distributed Tracing and Profiling
https://deepflow.io
Apache License 2.0
2.85k stars 314 forks source link

[BUG] application-k8s-pod-map 面板里面无法获取namespace 和workload的值 #6896

Open tjlqq opened 3 months ago

tjlqq commented 3 months ago

Search before asking

DeepFlow Component

Grafana Dashbaord

What you expected to happen

无法显示选项的值。 25e03dc7963b25025de66efce8f8a31 ck 查出来的 60 多个 pod 。当前 mysql 的最大连接数=200 、通过 mysql pod_group 表查出来的资源是没问题的 aceab210f57796bb28518d72378432d e3d6f25e5b5aa4f8c3636bea6b4c26d grafana 里面变量的 sql 都不一样 ; ck里面 是id 不是 pod_ns 82215835361a82167d8863db4b96c89

a1911b7febf802abf3af9f9bf2c8b6b

How to reproduce

No response

DeepFlow version

2024/06/13 18:05:04 ENV K8S_NODE_NAME_FOR_DEEPFLOW=10-90-91-17; K8S_NODE_IP_FOR_DEEPFLOW=10.90.91.17; K8S_POD_NAME_FOR_DEEPFLOW=deepflow-server-5f4cf9bb6d-7h9tv; K8S_POD_IP_FOR_DEEPFLOW=10.90.91.17; K8S_NAMESPACE_FOR_DEEPFLOW=deepflow flag provided but not defined: -v: Usage of deepflow-server: -f string Specify config file location (default "/etc/server.yaml") -v Display the version command terminated with exit code 2 [root@10-90-91-200 ~]# kubectl exec -it -n deepflow deploy/deepflow-server -- deepflow-server -v 2024/06/13 18:05:11 ENV K8S_NODE_NAME_FOR_DEEPFLOW=10-90-91-17; K8S_NODE_IP_FOR_DEEPFLOW=10.90.91.17; K8S_POD_NAME_FOR_DEEPFLOW=deepflow-server-5f4cf9bb6d-7h9tv; K8S_POD_IP_FOR_DEEPFLOW=10.90.91.17; K8S_NAMESPACE_FOR_DEEPFLOW=deepflow Name: deepflow-server community edition Branch: v6.4

和 [root@10-90-91-200 ~]# kubectl exec -it -n deepflow deploy/deepflow-server -- deepflow-server -v 2024/06/13 18:05:11 ENV K8S_NODE_NAME_FOR_DEEPFLOW=10-90-91-17; K8S_NODE_IP_FOR_DEEPFLOW=10.90.91.17; K8S_POD_NAME_FOR_DEEPFLOW=deepflow-server-5f4cf9bb6d-7h9tv; K8S_POD_IP_FOR_DEEPFLOW=10.90.91.17; K8S_NAMESPACE_FOR_DEEPFLOW=deepflow Name: deepflow-server community edition Branch: v6.4 CommitID: 71fd2e573c6d22f8a762769ded3a454b4b193bb5 RevCount: 9873 Compiler: go version go1.21.11 linux/amd64 CompileTime: 2024-06-13 04:21:20 [root@10-90-91-200 ~]# kubectl exec -it -n deepflow ds/deepflow-agent -- deepflow-agent -v Defaulted container "deepflow-agent" out of: deepflow-agent, configure-sysctl (init) 9872-4d97deafe634fece9ad1c9a9b9c35572573dece4 Name: deepflow-agent community edition Branch: v6.4 CommitId: 4d97deafe634fece9ad1c9a9b9c35572573dece4 RevCount: 9872 Compiler: rustc 1.75.0 (82e1608df 2023-12-21) CompileTime: 2024-06-12 04:27:5 CommitID: 71fd2e573c6d22f8a762769ded3a454b4b193bb5 RevCount: 9873 Compiler: go version go1.21.11 linux/amd64 CompileTime: 2024-06-13 04:21:20

DeepFlow agent list

[root@10-90-91-200 ~]# deepflow-ctl agent list 2024/06/13 18:06:10 open /run/secrets/kubernetes.io/serviceaccount/ca.crt: no such file or directory ID NAME TYPE CTRL_IP CTRL_MAC STATE GROUP EXCEPTIONS REVISION UPGRADE_REVISION
37 10-90-91-42-V47 K8S_VM 10.90.91.42 b4:96:91:a5:52:c3 NORMAL default v6.4 9872
40 10-90-91-41-V48 K8S_VM 10.90.91.41 e4:43:4b:f1:b9:e8 NORMAL default v6.4 9872
45 10-90-91-81-V27 K8S_VM 10.90.91.81 f4:8e:38:bf:11:c0 NORMAL default v6.4 9872
56 10-90-91-43-V41 K8S_VM 10.90.91.43 b4:96:91:a5:4f:e0 NORMAL default v6.4 9872
59 linux-10-90-2-11-W58 CHOST_VM 10.90.2.11 00:50:56:8c:22:dc NORMAL ack-sit-nginx CONTROLLER_SOCKET_ERROR,ANALYZER_SOCKET_ERROR v6.5.8 10490
60 10-90-91-76-V42 K8S_VM 10.90.91.76 56:6f:5f:d5:00:19 NORMAL default v6.4 9872
61 10-90-91-75-V52 K8S_VM 10.90.91.75 56:6f:5f:d5:00:18 NORMAL default

Kubernetes CNI

No response

Operation-System/Kernel version

3.10.0-1160.el7.x86_64

Anything else

No response

Are you willing to submit a PR?

Code of Conduct

tjlqq commented 3 months ago

bbdbc51d65f88693f1fb329a864cad1 7e8763ff53a044b8e9fab6a8e71226b node 60 多个 ck 相关查询信息

1473371932 commented 3 months ago

Hello, how many Kubernetes nodes are currently in the cluster? Has the deepFlow-agent been deployed on each node? If certain nodes lack deployment, it is essential to deploy them and reassess the outcome. Only resources generating traffic will be displayed within the namespace and workload environment variables. The agent can synchronize cluster resources via the API server; however, to collect traffic from specific resources, the DeepFlow agent must be deployed on the corresponding nodes.

tjlqq commented 3 months ago

谢谢回复。1.62个node.2,没有只部署了其中几台机器 ingess 节点机器。