Application Real-Time Monitoring Service (ARMS) stores traces, metrics, logs, and profiling data in two backends: Simple Log Service (SLS) and Managed Service for Prometheus. Query the stored data in SLS or Prometheus to build dashboards, filter by dimensions, or aggregate across services.
Storage in SLS or Managed Service for Prometheus does not incur additional fees. You are charged only for using ARMS. For details, see Billing (new version).
Retention summary
The following table summarizes retention periods across all ARMS sub-services.
| Sub-service | Data type | Retention |
|---|---|---|
| Application Monitoring / Managed Service for OpenTelemetry | Metric data | 90 days |
| Application Monitoring / Managed Service for OpenTelemetry | Trace data | 30 days |
| Application Monitoring / Managed Service for OpenTelemetry | Profiling data | 7 days |
| Real User Monitoring (RUM) | Log data | 30 days |
| Real User Monitoring (RUM) | Alert metric data | 90 days |
| Browser Monitoring | Observable data | 30 days |
Storage paths by sub-service
Each sub-service writes data to dedicated SLS LogProjects, Logstores, or Prometheus instances. Use the schema references to understand the field definitions for custom queries.
Do not delete the SLS LogProject or Prometheus instance that stores observable data. Deletion causes data loss and features become unavailable.
Application Monitoring and Managed Service for OpenTelemetry
| Data type | Storage path | Schema reference |
|---|---|---|
| Metric data | Prometheus instance: arms_metrics_<region-id>_cloud_<region> | Application monitoring metrics |
| Trace data | SLS LogProject: proj-xtrace-<encode>-<region-id>, Logstore: logstore-tracing | Trace Explorer parameters |
| Profiling data | Custom development is not supported | -- |
Real User Monitoring (RUM)
| Data type | Storage path | Schema reference |
|---|---|---|
| Log data | SLS LogProject: proj-xtrace-<encode>-<region-id>, Logstore: logstore-rum | Log data description |
| Alert metric data | Prometheus instance: rum-<region-id> | Alert metrics |
Browser Monitoring
| Data type | Storage path | Schema reference |
|---|---|---|
| Observable data | SLS LogProject: proj-rum-<encode>, Logstore: logstore-<encode>-search (one Logstore per monitored site) | Browser Monitoring fields |
Storage path examples
The following examples show resolved storage paths for the China (Hangzhou) region:
| Data type | Example path |
|---|---|
| Application metrics | arms_metrics_cn-hangzhou_cloud_hangzhou |
| Trace data (LogProject) | proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou |
| RUM log data (LogProject) | proj-xtrace-a91c22e2d3d346a756da6faee7c450bb-cn-hangzhou |
| RUM alert metrics | rum-cn-hangzhou |
| Browser Monitoring (LogProject) | proj-rum-a273c31f586675e474fd53847d2e3bb |
| Browser Monitoring (Logstore) | logstore-9a5e86167388885f104e9cc542c90bb-search |
Query stored data
Use the schema references in the tables above to build SLS or Prometheus queries on your stored data:
Trace analysis: Query
logstore-tracingto investigate spans. See Trace Explorer parameters.Metric dashboards: Query the
arms_metrics_*Prometheus instance to build custom dashboards. See Application monitoring metrics.RUM log queries: Query
logstore-rumto analyze RUM log data. See Log data description.