Observable data storage
The observable data generated in the sub-services of Application Real-Time Monitoring Service (ARMS), such as Application Monitoring, Managed Service for OpenTelemetry, or Real User Monitoring (RUM), can be stored in Simple Log Service and Managed Service for Prometheus. This allows you to perform custom development on the observable data and analyze it based on filter conditions or aggregation dimensions to meet custom analysis requirements in various scenarios.
Do not delete the Simple Log Service project or Prometheus instance that stores the observable data. Otherwise, the data will be lost and features will become unavailable.
Storage paths
Data storage in Simple Log Service or Managed Service for Prometheus does not incur fees. You are charged only for using ARMS. For more information about billing, see Billing (new version).
The following table describes the storage paths and duration:
Sub-service | Billable item | Storage duration | Storage path | References |
Application Monitoring/ Managed Service for OpenTelemetry | Metric data | 90 days | Prometheus instance: arms_metrics_<region-id>_cloud_<region> Example: arms_metrics_cn-hangzhou_cloud_hangzhou | |
Trace data | 30 days |
| ||
Profiling data | 7 days | Custom development is not supported. | - | |
RUM | Log data | 30 days |
| |
Alert metric data | 90 days | Prometheus instance: rum-<region-id> Example: rum-cn-hangzhou | ||
Browser Monitoring | Observable data | 30 days |
|
The following describes the observable data processing and data storage resources for Application Monitoring and RUM in CloudMonitor 2.0:
Computing resources
Sub-service
Task type
Purpose
Storage path
Application Monitoring/
Managed Service for OpenTelemetry
ScheduleSQL
Observable data processing
Simple Log Service project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Schedule Job Id: Random string within 32 characters, which can be used to view descriptions and scripts (SQL statements).
RUM
ScheduleSQL
Observable data processing
Simple Log Service project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Schedule Job Id: Random string within 32 characters, which can be used to view descriptions and scripts (SQL statements).
Storage resources
Sub-service
Billable item
Storage duration
Storage path
Application Monitoring/
Managed Service for OpenTelemetry
Metric data
90 days
Simple Log Service project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Simple Log Service MetricStore:
metricstore-apm-metrics-detail: Storage medium for detailed metrics.
The default bound Prometheus instance name is metricstore-apm-metrics-detail_{region-id}_{workspace}
metricstore-apm-metrics: Storage medium for aggregated metrics.
The default bound Prometheus instance name is metricstore-apm-metrics_{region-id}_{workspace}
metricstore-apm-metrics-custom: Storage medium for business trace analysis and custom metrics.
The default bound Prometheus instance name is metricstore-apm-metrics-custom_{region-id}_{workspace}
Trace data
30 days
Simple Log Service project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Simple Log Service Logstore: logstore-tracing
Profiling data
7 days
Simple Log Service project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Simple Log Service Logstore: logstore-profiling
RUM
Metric data
90 days
Simple Log Service project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Simple Log Service Metricstore: metricstore-rum-metrics
The default bound Prometheus instance name is rum-<region-id>
Log data
30 days
Simple Log Service project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Simple Log Service Logstore: logstore-rum
Storage redundancy
ARMS Application Monitoring and RUM data provide two types of storage redundancy: locally redundant storage and zone-redundant storage. These cover data redundancy mechanisms from single zone to multi-zone, ensuring data durability and availability. Currently, ARMS is upgrading its storage redundancy capabilities, with different regions having different status. The upgrade status is consistent with Simple Log Service. For more information about region-specific details, see Storage redundancy.
The service availability and pricing are the same for both locally redundant storage and zone-redundant storage in the ARMS data plane.
Storage redundancy type | Service availability |
Locally redundant storage | 99.9% |
Zone-redundant storage | 99.9% |