# ess-monitoring

Part of **ESS**

<!-- intent-backlink:auto -->

> 💡 **Path Selection**: This skill is one implementation path for [Configure scaling triggers (scheduled or event-based)](../../intent/ess-configure-triggers/SKILL.md). If you're unsure which path to take, check the routing skill first.

# Auto Scaling Monitoring Console Guide

## Operations Overview

| Operation | Console Entry | Prerequisites | Description |
|----------|---------------|---------------|-------------|
| Custom Monitoring Setup | Console > CloudMonitor > Application Groups, Custom Metrics | Java SDK dependencies configured, Application group ID available or created, Access keys (accAutoScalingKey and accAutoScalingSecret) ready | Configure and report custom metrics for use in Auto Scaling event-triggered tasks |

## Operation Steps

### Custom Monitoring Setup

**Navigation**: Console > CloudMonitor > Application Groups, Custom Metrics

**Prerequisites**:
- Java SDK dependencies configured
- Application group ID available or created
- Access keys (accAutoScalingKey and accAutoScalingSecret) ready

1. Go to the CloudMonitor console  
   - Element: **CloudMonitor console** (link) — located in the top navigation bar  
   - Notes: The console is accessible at https://cloudmonitor.console.aliyun.com. After loading, navigate to the **Application Groups** and **Custom Metrics** pages using the left-side menu.

2. Prepare your application to report custom metrics using the Java SDK  
   - Element: (none — external development step)  
   - Notes: This step occurs outside the console. Ensure your code uses the correct access keys and reports metrics to the specified application group. Data must comply with size and rate limits.

3. Verify that custom metrics appear in the CloudMonitor console  
   - Element: **Custom Metrics** (tab) — under the CloudMonitor navigation menu  
   - Notes: After successful reporting, metrics will appear within a few minutes. Use this view to confirm data ingestion before creating event-triggered scaling rules.

**Form Fields**: None (this operation primarily involves external SDK usage and console verification)

## FAQ

Q: Where do I find the CloudMonitor console?
A: You can access it directly at https://cloudmonitor.console.aliyun.com or through the main cloud console’s top navigation bar by clicking **CloudMonitor console**.

Q: Can I create an application group directly in the console for custom monitoring?
A: Yes, you can create and manage application groups in the **Application Groups** section of the CloudMonitor console before reporting custom metrics.

Q: What happens if I exceed the request quota for custom metric reporting?
A: Requests beyond the limit (10 per second) may be throttled. It is recommended to aggregate data locally before sending to avoid exceeding quotas.

Q: Do I need special permissions to report custom metrics?
A: Yes, your account must have permissions to write custom metrics to CloudMonitor and access the specified application group. Ensure your access keys have the necessary RAM policies attached.

Q: Can I use custom metrics immediately after reporting them?
A: Metrics typically appear in the console within 1–2 minutes. You must wait for them to be visible before referencing them in Auto Scaling event-triggered tasks.

## Pricing & Billing

### Billing Model
Per-request billing: you are charged for each custom metric data point reported to CloudMonitor.

### Price Reference

| Tier | Input Price |
|------|-------------|
| default | 0.001 / |

### Free Tier
 1000 

### Billing Notes
Reporting monitoring data is subject to limits. Aggregating data locally before sending is recommended for high-volume scenarios. Quota limits include a maximum of 10 requests per second and 100KB per request.