You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have setup a test cluster of 8 nodes, each of them containing 4 identical drives of 1TB. Then I proceed to install a prometheus server on another server connected to the same local network.
The used capacity metric is displayed twice (on the two charts circled in red on my screenshot) but the value differs from one chart to another.
I just uploaded a 50GB folder on this cluster, so it seems the right value is the second one (74.3 GiB).
Additional information
OS: Ubuntu server 22.04.02 MinIO version
minio version RELEASE.2023-03-13T19-46-17Z (commit-id=c7f7e67a100ce35af559e3f49a2ed0b67deaa919)
Runtime: go1.19.7 linux/amd64
License: GNU AGPLv3 <https://www.gnu.org/licenses/agpl-3.0.html>
Copyright: 2015-2023 MinIO, Inc.
Prometheus version
prometheus, version 2.43.0 (branch: HEAD, revision: edfc3bcd025dd6fe296c167a14a216cab1e552ee)
build user: root@8a0ee342e522
build date: 20230321-12:56:07
go version: go1.19.7
platform: linux/amd64
tags: netgo,builtinassets
Loadbalancer: None, everything is routed to the first node
The text was updated successfully, but these errors were encountered:
LeBovin
changed the title
[Bug] inconsistent data in monitoring
[Bug] inconsistent "used capacity" in monitoring
Mar 23, 2023
Hello
Context
I have setup a test cluster of 8 nodes, each of them containing 4 identical drives of 1TB. Then I proceed to install a prometheus server on another server connected to the same local network.
The used capacity metric is displayed twice (on the two charts circled in red on my screenshot) but the value differs from one chart to another.
I just uploaded a 50GB folder on this cluster, so it seems the right value is the second one (74.3 GiB).
Additional information
OS: Ubuntu server 22.04.02
MinIO version
Prometheus version
Loadbalancer: None, everything is routed to the first node
The text was updated successfully, but these errors were encountered: