All Products
Search
Document Center

Managed Service for Prometheus:Use Managed Service for Prometheus to monitor ECS instances

Last Updated:Aug 27, 2026

Monitor ECS instances in a VPC with Managed Service for Prometheus. Enable Host Monitor to auto-install exporters and collect metrics, then optionally discard unneeded metrics and configure alerting.

Workflow

To monitor ECS instances, complete these steps:

  1. Enable Host Monitor: Select a VPC to auto-install open source exporters. The managed Prometheus agent collects data automatically.

  2. (Optional) Modify Host Monitor: Change settings such as the service port to fix errors or meet new requirements.

  3. (Optional) Discard metrics: Drop unneeded metrics to reduce collection volume and costs.

  4. (Optional) Configure alerting: Set up alert rules to detect metric changes and troubleshoot issues promptly.

image

Prerequisites

1. Enable Host Monitor

Enabling Host Monitor for a VPC installs Node Exporter and Process Exporter on each ECS instance by default. The managed Prometheus agent then collects, stores, and visualizes data with unified alerting. About 1,000 metrics are collected per ECS instance per scrape.

1.1 Enable the component

  1. In the left-side navigation pane of the ARMS console, click Integration Center. In the Infrastructure section, click Host Monitor.image

  2. Select the VPC and configure parameters as described in Monitor ECS instances.image

  3. Click OK and wait 1 to 2 minutes.

1.2 Identify the Prometheus instance for your ECS instance

After enabling Host Monitor, verify which Prometheus instance is collecting data for your ECS instance. Each Prometheus instance is associated with the VPC you selected during setup, and instance names include VPC information for easy identification.

  1. Log on to the ARMS console. In the left-side navigation pane, choose Managed Service for Prometheus > Instances.

  2. In the instance list, find the Prometheus instance associated with the VPC you selected. Instance names include VPC information for easy identification.

  3. Click the instance name to open the details page and confirm that this instance is monitoring your ECS instance.

1.3 View the dashboards

  1. In the left-side navigation pane of the ARMS console, click Integration Management. On the Integrated Environments tab, click ECS Instance. Click the VPC ID to open the environment details page.image

  2. On the Component Management tab, click Dashboards in the Addon Type section to view the built-in Grafana dashboards.imageimage

    Note

    If the dashboards have no data, check the security group settings. For more information, see Why do the dashboards have no data?

2. (Optional) Modify Host Monitor

Modify Host Monitor settings such as service discovery, service port, or data collection interval.

2.1 Procedure

  1. In the left-side navigation pane of the ARMS console, click Integration Management. On the Integrated Environments tab, click ECS Instance. Click the VPC ID to open the environment details page.image

  2. Find the target exporter and clickSettings.image

  3. Adjust the settings and click OK. Parameter descriptions are in Monitor ECS instances.

2.2 Verification

  1. Refresh the page and click Settings to verify the changes.

  2. Check the dashboards to verify data accuracy. For more information, see the 1.3 View the dashboards section.

3. (Optional) Discard metrics

Discard unneeded metrics to simplify data analysis and reduce costs.

3.1 Procedure

  1. In the left-side navigation pane of the ARMS console, click Integration Management. On the Integrated Environments tab, click ECS Instance. Click the VPC ID to open the environment details page.image

  2. In the Discard Metrics section of the Metric Scraping tab, select the metrics to discard and click Update. For information about metrics, see Metrics.image

    Note

    You cannot discard the basic metrics about ACK clusters.

3.2 Verification

  1. Click Update and refresh the page to verify the changes.

  2. Check the dashboards to verify data accuracy. For more information, see the 1.3 View the dashboards section.

4. (Optional) Configure alerting

Configure alert rules to receive notifications when metric values change, enabling faster troubleshooting.

Managed Service for Prometheus supports both built-in and custom alert rules.

4.1 Configure built-in alert rules

Built-in alert rules generate events by default. Configure notifications manually.

  1. In the left-side navigation pane of the ARMS console, click Integration Management. On the Integrated Environments tab, click ECS Instance. Click the VPC ID to open the environment details page.image

  2. In the Addon Type section of the Component Management tab, click Alert Rule. Click View Alert Event or Edit to view or modify an alert rule.image

  3. Adjust the alert rule and click OK. Configuration details are in Prometheus alert rules.

4.2 Configure custom alert rules

Create custom alert rules if the built-in rules do not meet your requirements.

  1. In the left-side navigation pane of the ARMS console, click Integration Management. On the Integrated Environments tab, click ECS Instance. Click the VPC ID to open the environment details page.image

  2. On the Component Management tab, click the VPC next to Default Metric Storage in the Basic Information section.image

  3. On the Alert rules page, create, modify, or view custom alert rules. See Prometheus alert rules.image

4.3 Verification

  1. Refresh the page to verify the changes.

  2. Create a low-risk test alert rule, trigger it, and verify that it works as expected.

    Note

    Notification delivery depends on the alert rule configuration.

FAQ

Why do the dashboards have no data?

The ECS instance security groups may not allow the required access. Ensure the following:

Each ECS instance's security group must allow inbound access from 100.64.0.0/10 and 192.168.0.0/18 to the Node Exporter port (default: 9100) and Process Exporter port (default: 9256). Use your custom ports if modified. For information about how to view the security group rules of an ECS instance, see Search for security groups.

Why was Node Exporter not automatically installed on the ECS instance?

Check the following:

  1. Verify that the ECS instance is running.

  2. Check whether an open source Node Exporter is already installed and using port 9100. If so, go to the Component Management tab, find the Alibaba Cloud Node Exporter, and click Settings to change the port.

How do I check whether Node Exporter has been installed?

Visit http://<ECS-IP>:<PORT>/metrics. If metric data is returned, Node Exporter is installed and running.

How do I manually configure security group rules?

Log on to the ECS console. Add an inbound rule to each ECS instance's security group to allow access from the VPC CIDR block to the Node Exporter port (default: 9100) and Process Exporter port (default: 9256). Use your custom ports if modified.

How do I troubleshoot network issues when integrating ECS instances?

Ensure mutual network access between ECS instances and the Prometheus agent within the VPC. Verify the VPC route table for correct traffic direction, then check that firewall and security group rules allow the traffic.

Why is the metric data inaccurate or missing?

If Node Exporter and Process Exporter are enabled, verify that they are running. Use cURL to query the exporter metrics endpoints and confirm that data is returned. If errors occur, check the exporter logs.

How do I enable process status data collection?

Process Exporter collects process status data on port 9256 by default. Allow port 9256 in the security group of each ECS instance. Process data collection consumes minimal system resources. However, if resources are insufficient, proceed with caution.