Connecting Running Environments to AOM

Procedure

1. Log in to the AOM 2.0 console.
2. In the navigation pane on the left, choose Access > Access Center. (To switch from the new access center to the old one, click Back to Old Version in the upper right corner.)
3. In the Prometheus Running Environments panel on the right, click the target card and perform the operations listed in the following table if needed.

   Table 1 Connecting Prometheus running environments to AOM

   Card	Related Operation
   Cloud Container Engine (CCE) (ICAgent)	Uses ICAgent to collect CCE cluster metrics. By default, ICAgent is installed when you purchase a CCE cluster and node. ICAgent automatically reports CCE cluster metrics to AOM. Click the Cloud Container Engine (CCE) (ICAgent) card to view the CCE cluster metrics that can be ingested. For details about the CCE cluster metrics that are reported to AOM, see Basic Metrics: VM Metrics. To use Prometheus to collect CCE cluster metrics and report them to AOM, see Using Prometheus Monitoring to Monitor CCE Cluster Metrics.
   Cloud Container Instance (CCI)	CCI automatically reports metrics to AOM as ready-to-use data. No manual configuration is required. Click the Cloud Container Instance (CCI) card to view the CCI metrics that can be ingested. For details about the CCI metrics that are reported to AOM, see Basic Metrics: VM Metrics.
   Elastic Cloud Server (ECS)	Click the Elastic Cloud Server (ECS) card. In the displayed dialog box, install the Node Exporter provided by Prometheus. The information and running metrics of Linux hosts can then be collected. For details, see Connecting ECSs to AOM.

Connecting ECSs to AOM

Node Exporter is provided by Prometheus to collect information about Linux hosts, including the CPU, memory, load, file system, and network. You can install Node Exporter on an ECS and create a collection task. Related metrics can then be reported to AOM.

• Constraints

  A host supports only one Node Exporter.

• Prerequisites
  • The UniAgent has been installed and is running.
  • A Prometheus instance for ECS has been created.

1. Log in to the AOM 2.0 console.
2. In the navigation pane, choose Access > Access Center.
3. On the Prometheus Running Environments panel, click Elastic Cloud Server (ECS).
4. On the Procedure tab page of the Elastic Cloud Server (ECS) dialog box, perform the installation as prompted.
   1. Select a target Prometheus instance for ECS from the drop-down list.
   2. Install Node Exporter: Select one or more hosts where Node Exporter is to be installed.

5. Click Install to install Node Exporter.
   • After the installation is complete, use UniAgent to create a collection task. Node Exporter can then collect host metrics. For the metrics collected by Node Exporter, see Basic Metrics: Node Exporter Metrics. By default, both the values of Metric Collection Interval (s) and Metric Collection Timeout (s) are 60. The two values cannot be changed.
   • You can also perform the following operations on the Collection Tasks tab page under Elastic Cloud Server (ECS).

     Table 2 Related operations

     Operation	Description
     Searching for a collection task	You can search for collection tasks by collection task, collection status, host IP address, or host name.
     Refreshing a collection task	Click in the upper right corner of the collection task list to obtain the latest information.
     Deleting a collection task	Click Delete in the Operation column.
     Starting or stopping a collection task	Click the button in the Start/Stop column of a collection task to start or stop it.