Details
-
Bug
-
Status: Done
-
Medium
-
Resolution: Fixed
-
None
-
None
-
7
-
Yes
-
Yes
-
[obsolete] Server Integrations
Description
Impact on the user:
- The user is unable to see the proper "node/container" parameters of OS-level metrics in DBaaS
STR:
- Setup PMM
- configure DBaaS
- provide correct Server Address in settings
- Start default small MySQL DB Cluster (3 nodes, 1 cpu, 2 GM memory, 25 GB)
- Go to dashboards, Mysql Instance summary
Expected Result:
- At the bottom, the user can see Node/container metrics
memory 2 GB, 25Gb disk
Given Result:
- some strange/big numbers. Probably all cluster parameters, not specific Mysql
- One can see memory available on kubernetes node, not the container itself because /proc/meminfo is not namespaced. Thus even though container is limited by cgroups to 2GB of memory, it could not be seen.
jan@jan-Latitude-5591:~$ kubectl exec -it df7143-pxc-0 -- bash Defaulting container name to pmm-client. Use 'kubectl describe pod/df7143-pxc-0 -n default' to see all of the containers in this pod. bash-4.2$ free total used free shared buff/cache available Mem: 16417904 3957868 10273744 642392 2186292 11869520 Swap: 0 0 0
Workaround:
N/A
Suggested implementation
- use https://github.com/google/cadvisor instead of node_exporter
Original report:
Notes:
https://github.com/google/cadvisor/blob/master/docs/storage/prometheus.md
Attachments
Issue Links
- is blocked by
-
PMM-9496 Cannot create or update vmagent service k8s
-
- Done
-
-
PMM-8214 Ability to collect Kubernetes cluster metrics
-
- Done
-
- is cloned by
-
PMM-10039 Components Upgrade: VictoriaMetrics Operator 0.16 to 0.24
-
- Done
-
-
PMM-10040 Relabel metrics from cadvisor
-
- Done
-
- relates to
-
PMM-10254 Dashboards: Memory Available displays different values
-
- Done
-
- links to
(2 links to, 3 mentioned in)