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
Copy file name to clipboardExpand all lines: doc/cephfs/metrics.rst
+52Lines changed: 52 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,6 +66,40 @@ CephFS exports client metrics as :ref:`Labeled Perf Counters`, which could be us
66
66
- Gauge
67
67
- Number of bytes written in input/output operations generated by all processes
68
68
69
+
Subvolume Metrics
70
+
-----------------
71
+
72
+
CephFS exports subvolume metrics as :ref:`Labeled Perf Counters`, which could be used to monitor the subvolume performance. CephFS exports the below subvolume metrics.
73
+
Subvolume metrics are aggregated within sliding window of 30 seconds (default value, configurable via the ``subv_metrics_window_interval`` parameter, see :ref:`MDS config reference`).
74
+
In large Ceph clusters with tens of thousands of subvolumes, this parameter also helps clean up stale metrics.
75
+
When a subvolume’s sliding window becomes empty, it's metrics are removed and not reported as “zero” values, reducing memory usage and computational overhead.
76
+
77
+
.. list-table:: Subvolume Metrics
78
+
:widths: 25 25 75
79
+
:header-rows: 1
80
+
81
+
* - Name
82
+
- Type
83
+
- Description
84
+
* - ``avg_read_iops``
85
+
- Gauge
86
+
- Average read IOPS (input/output operations per second) over the sliding window.
87
+
* - ``avg_read_tp_Bps``
88
+
- Gauge
89
+
- Average read throughput in bytes per second.
90
+
* - ``avg_read_lat_msec``
91
+
- Gauge
92
+
- Average read latency in milliseconds.
93
+
* - ``avg_write_iops``
94
+
- Gauge
95
+
- Average write IOPS over the sliding window.
96
+
* - ``avg_write_tp_Bps``
97
+
- Gauge
98
+
- Average write throughput in bytes per second.
99
+
* - ``avg_write_lat_msec``
100
+
- Gauge
101
+
- Average write latency in milliseconds.
102
+
69
103
Getting Metrics
70
104
===============
71
105
@@ -130,3 +164,21 @@ The metrics could be scraped from the MDS admin socket as well as using the tell
130
164
}
131
165
}
132
166
]
167
+
168
+
The subvolume metrics are dumped as a part of the same command. The ``mds_subvolume_metrics`` section in the output of ``counter dump`` command displays the metrics for each client as shown below::
0 commit comments