ARMS writes observable data from Application Monitoring, Managed Service for OpenTelemetry, and Real User Monitoring to your Simple Log Service (SLS) or Managed Service for Prometheus instances. You can use the stored full data for custom development. You can also combine filter conditions and aggregation dimensions to perform real-time analysis for various scenarios.
Do not delete the SLS projects or Prometheus instances that store your observable data. Otherwise, the data will be lost and related features will become unavailable.
Storage paths
Data that ARMS stores in SLS or Managed Service for Prometheus does not incur extra charges. You are charged only for ARMS. For more information, see Product Billing (New).
The following table describes the storage paths and usage.
Cloud product | Data type | Retention period | Storage path | Field description |
Application Monitoring/ Managed Service for OpenTelemetry | Metrics data | 90 days | Prometheus instance: arms_metrics_<region-id>_cloud_<region> Example: arms_metrics_cn-hangzhou_cloud_hangzhou | For more information, see Application Monitoring metrics. |
Trace data | 30 days |
| For more information, see Trace analysis parameters. | |
Profiling data | 7 days | Custom development is not supported. | - | |
Real User Monitoring | Log data | 30 days |
| For more information, see Log data description. |
Alert metrics data | 90 days |
| For more information, see RUM alert rule metrics. | |
Browser Monitoring | Browser Monitoring data | 30 days |
| For more information, see Browser Monitoring data description. |
The following describes the observable data processing and data storage resources for Application Monitoring and Real User Monitoring in CloudMonitor 2.0:
Computing resources
Cloud product
Task type
Purpose
Storage path
Application Monitoring/
Managed Service for OpenTelemetry
ScheduleSQL
Observable data processing
SLS Project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Schedule Job ID: A random string of up to 32 characters. Use the ID to view the description and script (SQL statement).
Real User Monitoring
ScheduleSQL
Observable data processing
SLS Project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Schedule Job ID: A random string of up to 32 characters. Use the ID to view the description and script (SQL statement).
Storage resources
Cloud product
Data type
Retention period
Storage path
Application Monitoring/
Managed Service for OpenTelemetry
Metrics data
90 days
SLS Project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
SLS MetricStore:
metricstore-apm-metrics-detail: Storage medium for detailed metrics.
The name of the default attached Prometheus instance is metricstore-apm-metrics-detail_{region-id}_{workspace}
metricstore-apm-metrics: Storage medium for aggregated metrics.
The name of the default attached Prometheus instance is metricstore-apm-metrics_{region-id}_{workspace}
metricstore-apm-metrics-custom: Storage medium for business trace analysis and custom metrics.
The name of the default attached Prometheus instance is metricstore-apm-metrics-custom_{region-id}_{workspace}
Trace data
30 days
SLS Project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
SLS Logstore: logstore-tracing
Profiling data
7 days
SLS Project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
SLS Logstore: logstore-profiling
Real User Monitoring
Metrics data
90 days
SLS Project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
SLS Metricstore: metricstore-rum-metrics
The name of the default attached Prometheus instance is rum-<region-id>
Log data
30 days
Project: proj-xtrace-<encode>-<region-id>
Example: proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou
Logstore: logstore-rum
Data redundancy
ARMS Application Monitoring and Real User Monitoring support two types of data redundancy: locally redundant storage and zone-redundant storage. Both storage types use data redundancy mechanisms that span from a single zone to multiple zones to ensure data durability and availability. ARMS is currently upgrading its data redundancy feature. The status of this feature varies by region and is consistent with the upgrade status of Simple Log Service. For more information about specific regions, see Data Redundancy.
On the ARMS data plane, locally redundant storage and zone-redundant storage have the same service availability and price.
Redundancy type | Service availability |
Locally redundant storage | 99.9% |
Zone-redundant storage | 99.9% |