This topic describes how to ingest metrics from Alibaba Cloud Vector Retrieval Service for Milvus into Cloud Monitor 2.0.
Prerequisites
To ingest metrics, you must activate Observability Prometheus Edition and Hybrid Cloud Monitoring.
Limits
Only Cloud Monitor metric ingestion is supported.
If you use a RAM user to ingest metrics, assign the
AliyunCloudMonitorFullAccesssystem policy to the user.
Pricing
Ingesting metrics incurs Hybrid Cloud Monitoring real-time export fees and Observability Prometheus Edition fees.
Data ingestion
Log on to the Cloud Monitor 2.0 console. After selecting your target workspace, click Integration Center in the navigation bar, then click Vector Retrieval Service for Milvus metrics to start ingestion.
Create a new or select an existing Policy Name. Check the observable data you want to ingest based on your needs, then click OK.
Observable data
Configuration
Monitoring Metrics for Milvus Vector Retrieval Service
Tag key: Specify the keys of instance tags to enrich your metrics. Separate multiple keys with commas.
Enable all tags: Whether to enable all tags. Enabled by default.
After ingestion, view the ingested entities and related observable data in Entity Explorer.
Storage policy
After ingestion, Cloud Monitor creates a corresponding Prometheus instance to store the observable data.
Data type | Default storage location | Notes |
Metric | Prometheus instance: RegionShare:{{workspaceName}}:{{regionId}} | None |
Uninstall or modify ingestion policies
To cancel or modify ingestion, go to the Integration Center > Provisioning page, find the relevant ingestion policy, and click Edit or Delete.