Docs

Cloud Monitor

Exporting Monitoring Data to Prometheus

Exporter change log

This topic records the version update logs of the Exporter.

April 2026

Versions	Descriptions	Resources
v1.4.0	Added support for exporting monitoring data to self-managed Prometheus via the Remote Write method.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.4.0
v1.4.0			Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_v1.4.0.tar.gz

January 2026

Versions	Descriptions	Resources
v1.3.0	Added the historical data backfill feature, which allows you to manually backfill data that is lost due to export interruption. Optimized query time alignment and fixed the issue of inaccurate data for some metrics when the built-in metric latency parameter is applied. LimitQPSGetMetricData supported adaptive rate limiting for metadata requests.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.3.0
v1.3.0			Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_v1.3.0-ve.tar.gz

December 2025

Versions	Descriptions	Resources
v1.2.3	Fixed the issue of round timeouts for account-level metrics under the adaptive rate limiting mode.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.2.3
v1.2.3			Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_v1.2.3.tar.gz

November 2025

Versions	Descriptions	Resources
v1.2.2	Improved metric export stability.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.2.2
v1.2.2	Improved metric export stability.		Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_v1.2.2.tar.gz

October 2025

Versions	Descriptions	Resources
v1.2.1	Supported exporting based on Dimensions, which allows you to configure metric-level and product-level ExtraDimensions.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.2.1
v1.2.1			Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_v1.2.1.tar.gz

September 2025

Versions	Descriptions	Resources
v1.2.0	Optimized the metric conflict handling mechanism. When an error occurs during metric export, the system will record the error log and continue processing other metrics, which enhances system fault tolerance. Supported instance filtering and metric export based on cloud product metadata fields. In the full configuration StatisticsType, the default aggregation function is changed from FIRST to LAST to reduce the default metric export latency.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.2.0
v1.2.0			Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_v1.2.0.tar.gz

June 2025

Versions	Descriptions	Resources
v1.1.0	Supported exporting multiple Projects.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.1.0
v1.1.0	Supported exporting multiple Projects.		Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_v1.1.0.tar.gz

May 2025

Versions	Descriptions	Resources
v1.0.22	Supported metric data export at the cloud product account level.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.0.22
v1.0.22			Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_1.0.22.tar.gz

March 2025

Versions	Descriptions	Resources
v1.0.21	Switched the default Schema to the HTTPS request method and added the DisableSSL parameter. Take note of the following situation during the upgrade: To maintain the same HTTP request method as previous versions, configure DisableSSL. DisableSSL: [true \| default false]	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.0.21
v1.0.21			Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_1.0.21.2.tar.gz

November 2024

Versions	Descriptions	Resources
v1.0.20-p1	Supported enabling metric caching to ensure consistency of metric data at the same timestamp. Due to the metric reporting logic of some products, metric data may experience latencies and offsets. As a result, multiple monitoring requests for the same metric within a certain time range may obtain different data for the same timestamp, which leads to data inconsistency. To address the preceding issue, you can enable metric caching to discard subsequent monitoring data with the same timestamp. This ensures monitoring data consistency. Related parameters: EnableMetricCache: [ Boolean \| default false ] #某个指标没有命中缓存CacheMaxMissCount次数后，缓存会移除该指标戳信息 CacheMaxMissCount: [ Integer \| default 3 ] Parameter changes: The default value of BatchInstanceCount is set to 50.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:v1.0.20-p1
v1.0.20-p1			Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_1.0.20.tar.gz

September 2024

Versions	Descriptions	Resources
v1.0.19	Added the readiness/monitoring check API.	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:1.0.19
v1.0.19	Added the readiness/monitoring check API.		Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_1.0.19.tar.gz

August 2024

Versions	Descriptions	Resources
v1.0.18	Feature updates Added ExtraLabels and ExtraLabelsWithTagNameRegex. These parameters are related to instance metadata exporting, such as instance tags, projects, and custom attributes. Added the Products parameter for product-level configuration. Added the custom StatisticsType parameter. Added collection configuration at the custom metric granularity. Updated self-monitoring metrics. GetMetricData supported retries (3 times by default) after rate limiting is triggered. Added the adaptive rate limiting feature. By default, if LimitQPSGetMetricData and DataConcurrency are not specified, the Exporter will dynamically adjust QPS and concurrency parameters to distribute requests and minimize the risk of rate limiting. Added the retry capability in some failure scenarios. Parameter changes EnableDynamicDelaySecond: This configuration will no longer take effect. DelaySeconds: DelaySeconds is migrated to QueryRangeSeconds by default. We recommend that you use the QueryRangeSeconds parameter. Upgrade considerations The version is compatible with configurations from versions earlier than 1.0.18 by default. By default, instance metadata and project/tag information will not be exported. If you want to export the preceding information, you can add global configuration or product-level configuration. ExtraLabels: - 'Name' - 'ProjectName' ExtraLabelsWithTagNameRegex: - 'volc.env.*' To specify custom product-level configuration, we recommend that you migrate the Namespaces parameter to the Products parameter. Example: Configuration for versions earlier than 1.0.18 Namespaces: - "VCM_Redis" - "VCM_RDS_MySQL" Configuration for 1.0.18 and later Products: - Namespace: "VCM_Redis" ExtraLabels: ["ZoneIds"] - Namespace: "VCM_RDS_MySQL" ExtraLabels: ["InstanceType"]	Image address: cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:1.0.18
v1.0.18			Binary file: byteapm.cloud_monitor.cloud_monitor_exporter_1.0.18.tar.gz

May 2024

Versions	Descriptions	Image address
v1.0.17-rc0	Provided multiple methods of pulling data, which can handle certain network jitters in different scenarios. Enhanced Exporter self-monitoring metrics. Supported configuring AK and SK by using environment variables. Supported more log levels.	cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:1.0.17-rc0

December 2023

Versions	Descriptions	Image address
v1.0.16.1	Supported configuring different latencies for different cloud products. This resolves the issue of missing data in extreme cases because latencies are not configured. Supported dynamic latency and time offset. The Exporter dynamically adjusts the time range for querying data to ensure that each pull retrieves valid and complete data.	cloud-monitor-cn-beijing.cr.volces.com/cm/cloud-monitor-exporter:1.0.16.1

Last updated: 2026.07.10 14:02:22