Docs

Cloud Monitor

Announcement of Changes to Cloud Service Metrics

Change log of Milvus metrics

The Cloud Monitor team will soon adjust the monitoring metrics for the Milvus vector database, aiming to provide you with a more accurate and comprehensive monitoring experience.

tip

For cloud product metrics and details, see Cloud product metrics query.

October 2026

MetricName	SubNamespace	Type	Description	Impact
Proxy_Memory_Usage	resource	Unit change	The metric unit has changed from Bits(IEC) to Bytes(IEC).	This change does not affect the normal operation of cloud product instances and your business. Monitoring dashboards will display data based on the updated metrics. Alert rules remain unchanged and active. Alert notifications will be sent according to the settings in alert rules.
QueryNode_Memory_Usage
DataNode_Memory_Usage
IndexNode_Memory_Usage
MixCoord_Memory_Usage
StreamingNode_Memory_Usage

March 2026

MetricName	SubNamespace	Type	Description	Impact
ReadQPS	performance	Unit change	The metric unit will change from None to Count/Second.	This change does not affect the normal operation of cloud product instances and your business. Monitoring dashboards will display data based on the updated metrics. Alert rules remain unchanged and active. Alert notifications will be sent according to the settings in alert rules.
ReadVPS
WriteQPS
InsertVPS
UpsertVPS
DeleteVP

February 2026

MetricName	SubNamespace	Type	Description	Impact
SearchRequestVPS	collection	Metric deprecation	-	This change does not affect the normal operation of cloud product instances and your business. Related charts disappear from the monitoring dashboard, and you cannot specify the corresponding metrics during queries. If an exclamation mark (!) is added before an existing alert rule, it indicates that the alert rule contains a deprecated metric, and the alert will no longer be triggered. You need to remove the deprecated metric from the alert rule. If you do not remove or update the deprecated metric for an existing alert template, you cannot save the template. If you configured this metric in a custom dashboard using the Grafana add-on, the related monitoring data becomes unavailable. If you have configured this metric by using a custom observability dashboard, the related monitoring data will be unavailable.
SearchRequestVPSV3
QueryNodeSegmentNum
StoredBinlogSize

July 2025

MetricName	SubNamespace	Type	Description	Impact
RoleNodeNumber	function	Usage deprecation	Before the change, the usage purpose of the metric was alerting. After the change, the usage purpose of the metric is none.	This change does not affect the normal operation of cloud service instances and your business. Monitoring dashboards can still display data based on metrics. If an exclamation mark (!) is added before an existing alert rule, it indicates that the alert rule contains an invalid metric, and the alert will no longer be triggered. You need to modify the metric in the alert rule. If you do not remove or update the metric for an existing alert template, you cannot save the template.
CollectionCnt	meta	Usage deprecation	Before the change, the usage purpose of the metric was consumption. After the change, the usage purpose of the metric is none.	This change does not affect the normal operation of cloud product instances and your business. The corresponding metric cannot be queried during cloud product metric queries. Metrics cannot be retrieved or exported through the Grafana plug-in, API, or exporter, with a message indicating that the metric does not exist.

May 2025

MetricName	SubNamespace	Type	Description	Impact
NodeNumber	resource	Usage deprecation	Before the change, the usage purpose of the metric was alerting. After the change, the usage purpose of the metric is none.	This change does not affect the normal operation of cloud service instances and your business. Monitoring dashboards can still display data based on metrics. If an exclamation mark (!) is added before an existing alert rule, it indicates that the alert rule contains an invalid metric, and the alert will no longer be triggered. You need to modify the metric in the alert rule. If you do not remove or update the metric for an existing alert template, you cannot save the template.

Last updated: 2026.10.10 11:01:05