Historical monitoring
Historical monitoring
Where the live monitoring views show what's happening right now, these views look backward —— performance and utilization trends over a date range, which volumes have been busiest, and exactly how much physical space each volume is really reserving.
For the two trend views (performance and utilization history), if you set an end date in the future, StorONE projects a trend forward from your recent history rather than showing real data —— useful for a rough "at this rate" projection, but worth keeping in mind when you see it.
Performance history
monitoring performance history plots IOPS, throughput, latency, and I/O size over a date range, either system-wide or scoped to an application (optionally further scoped to specific volumes within it). Choose to see read-only, write-only, or combined read+write figures.
Using the web interface
- Open Monitoring > Performance and switch to the historical view.
- Under Entity Selection, choose System for a system-wide view, or an Application (and optionally specific Volumes within it).
- Under Counter Selection, choose which counters to plot
—— IOPS, Throughput, Latency, I/O Size. All four are shown by default. - Under Read/Write Selection, choose Read Only, Write Only, or Aggregate Reads/Writes.
- Under Date Selection, set the date range and sampling interval, then confirm to view the chart.
Using the CLI
monitoring performance history (--system | --application=<name> [--volumes=<name...>]) [--iops] [--throughput] [--latency] [--iosize] [--readOnly | --writeOnly | --aggrReadsWrites] [--fromDate=<date>] [--toDate=<date>] [--utcTime] [--interval=<interval>] [--interactiveChart | --saveChart]
| Option | Description |
|---|---|
--system |
See system-wide performance. |
--application=<name> |
See results for an application. |
--volumes=<name...> |
See results for specific volumes. |
--iops |
Show input/output operations per second. |
--throughput |
Show throughput. |
--latency |
Show latency. |
--iosize |
Show I/O size. |
--readOnly |
Show only read stats. |
--writeOnly |
Show only write stats. |
--aggrReadsWrites |
Combine read and write stats. |
--fromDate=<date> |
Start of the date range, ISO 8601 (YYYY-MM-DDTHH:MM:SS). Defaults to 30 days ago. |
--toDate=<date> |
End of the date range, ISO 8601. Defaults to now. A future date triggers a projected trend. |
--utcTime |
Show timestamps in UTC instead of local time. |
--interval=<interval> |
Sampling interval, in minutes. |
--interactiveChart |
Create an interactive chart instead of text output. Windows CLI only. |
--saveChart |
Create a chart and save it to a file without displaying it. Windows CLI only. |
Examples
System-wide latency and IOPS for the last 30 days:
monitoring performance history --system --iops --latency
Throughput history for a specific volume over a specific week:
monitoring performance history --application training --volumes videos --throughput --fromDate 2026-09-01T00:00:00 --toDate 2026-09-07T23:59:59
Combined read+write IOPS for the whole finance application, sampled hourly:
monitoring performance history --application finance --iops --aggrReadsWrites --interval 60
Utilization history
monitoring utilization history plots resource utilization —— HDD, SSD, NVMe, CPU, and memory —— over a date range, per node or aggregated across all nodes.
Using the web interface
- Open Monitoring > Utilization and switch to the historical view.
- Under Node Selection, optionally choose a specific Node, and/or turn on Aggregate to combine all nodes.
- Under Resource Type Selection, choose which resources to plot
—— HDD, SSD, NVMe, CPU, Memory. All are shown by default. - Under Date Selection, set the date range and sampling interval, then confirm to view the chart.
Using the CLI
monitoring utilization history [--node=<name>] [--aggr] [--hdd] [--ssd] [--nvme] [--cpu] [--memory] [--fromDate=<date>] [--toDate=<date>] [--utcTime] [--interval=<interval>] [--interactiveChart | --saveChart] [--force]
| Option | Description |
|---|---|
--node=<name> |
Filter results for a specific node. |
--aggr |
Aggregate results for all nodes. |
--hdd |
Show HDD utilization. |
--ssd |
Show SSD utilization. |
--nvme |
Show NVMe utilization. |
--cpu |
Show CPU utilization. |
--memory |
Show memory utilization. |
--fromDate=<date> |
Start of the date range, ISO 8601. Defaults to 30 days ago. |
--toDate=<date> |
End of the date range, ISO 8601. Defaults to now. A future date triggers a projected trend. |
--utcTime |
Show timestamps in UTC instead of local time. |
--interval=<interval> |
Sampling interval, in minutes. |
--interactiveChart |
Create an interactive chart instead of text output. Windows CLI only. |
--saveChart |
Create a chart and save it to a file without displaying it. Windows CLI only. |
--force |
Don't ask for confirmation when the results include predicted (projected) values. |
Examples
CPU and memory utilization for node s1-node-01 over the last 30 days:
monitoring utilization history --node s1-node-01 --cpu --memory
HDD utilization aggregated across all nodes for a specific month:
monitoring utilization history --hdd --aggr --fromDate 2026-08-01T00:00:00 --toDate 2026-08-31T23:59:59
Top volumes
monitoring top volumes ranks volumes by one of four measures: current data capacity consumption, current snapshot/retention capacity consumption, IOPS, or latency. Only one measure can be selected at a time. The IOPS and latency rankings can be scoped to a date range (--fromDate/--toDate); the two capacity-based rankings always reflect the current state and don't accept a date range. Use --limit to cap how many volumes are returned.
Using the web interface
- Open Monitoring > Top Volumes.
- Under Sort By, choose one ranking
—— User Data Consumed Size, Retention Consumed Size, IOPS, or Latency. - For the IOPS or Latency rankings, optionally set a date range; otherwise confirm to see the current top volumes.
Using the CLI
monitoring top volumes (--userDataConsumedSize | --retentionConsumedSize | --iops | --latency) [--fromDate=<date>] [--toDate=<date>] [--limit=<numbers>] [--interactiveChart | --saveChart]
| Option | Description |
|---|---|
--userDataConsumedSize |
Show top volumes by data capacity consumption. |
--retentionConsumedSize |
Show top volumes by data retention (snapshot) capacity consumption. |
--iops |
Show top volumes by input/output operations per second. |
--latency |
Show top volumes by latency. |
--fromDate=<date> |
Start of the date range, ISO 8601. Not supported with --userDataConsumedSize or --retentionConsumedSize. |
--toDate=<date> |
End of the date range, ISO 8601. Not supported with --userDataConsumedSize or --retentionConsumedSize. |
--limit=<numbers> |
Limit the number of top volumes shown. |
--interactiveChart |
Create an interactive chart instead of text output. Windows CLI only. |
--saveChart |
Create a chart and save it to a file without displaying it. Windows CLI only. |
Examples
The 10 busiest volumes by IOPS right now:
monitoring top volumes --iops --limit 10
The volumes consuming the most snapshot/retention capacity:
monitoring top volumes --retentionConsumedSize
The 5 highest-latency volumes over the past week:
monitoring top volumes --latency --limit 5 --fromDate 2026-09-15T00:00:00 --toDate 2026-09-22T00:00:00
Reserve space
monitoring reserve current shows exactly how much physical space each volume is reserving on disk, broken down by which drive tier —— HDD, SSD, or NVMe —— that space lives on. This includes the vRAID redundancy overhead (the K parity fragments), so the figure reported here is typically larger than the volume's logical data size. Choose whether to see the reserve for user data or for metadata.
Using the web interface
Open Monitoring > Reserve, then choose Data or Metadata.
Using the CLI
monitoring reserve current (--data | --metadata)
| Option | Description |
|---|---|
--data |
Show data reserve. |
--metadata |
Show metadata reserve. |
Examples
Reserved data space per volume, broken out by tier:
monitoring reserve current --data
Reserved metadata space per volume:
monitoring reserve current --metadata
Next: Tiering monitoring —— autotiering evacuation activity and usage distribution. See also: Health and capacity ·· Live monitoring