Connecting Running Environments to AOM

Configuring Running Environment Connection to AOM

1. Log in to the AOM 2.0 console.
2. In the navigation pane on the left, choose Access Center > Access Center to go to the new access center.

   If the old access center is displayed, click Try New Version in the upper right corner.

3. Select the check box next to Running environments under Types to filter out the running environment cards.
4. Click Ingest Metric (AOM) to quickly ingest metrics or click Ingest Log (LTS) Details to check documents related to log ingestion.
   • Ingest Metric (AOM): AOM supports metric ingestion for running environments. By clicking Ingest Metric (AOM), you can quickly ingest metrics of running environments.
   • Ingest Log (LTS) Details: AOM provides an entry for ingesting logs of running environments to LTS.
     • By clicking Details on Ingest Log (LTS) Details, you can check the documents related to log ingestion. You can ingest logs according to the documents.
     • By clicking Ingest Log (LTS) on Ingest Log (LTS) Details, you can quickly ingest logs of running environments.

   Table 1 Connecting running environments to AOM

   Card	Related Operation
   Elastic Cloud Server (ECS)	ECS is a cloud server that allows on-demand allocation and elastic computing capability scaling. It helps you build a reliable, secure, flexible, and efficient application environment to ensure that your services can run stably and continuously, improving O&M efficiency. For details, see: Ingesting ECS Text Logs to LTS. Ingesting ECS Metrics (AOM)
   Bare Metal Server (BMS)	BMS is a high-performance, high-security physical server on the cloud. For details, see Ingesting BMS Text Logs to LTS.
   Cloud Container Engine (CCE)	CCE is a high-performance, high-reliability service through which enterprises can manage containerized applications. CCE supports native Kubernetes applications and tools, allowing you to easily establish a container runtime environment on the cloud. For details, see: CCE metric ingestion to AOM: By default, ICAgents are installed on CCE clusters upon your purchase. CCE cluster metrics will be automatically reported to AOM. Ingesting CCE Application Logs to LTS
   Cloud Container Instance (CCI)	CCI provides a serverless container engine that eliminates the need to manage clusters or servers. In only three steps, you can create a workload. CCI automatically reports metrics to AOM as ready-to-use data.
   Self-Managed Kubernetes Cluster	Kubernetes is an open-source container orchestration system that automates the deployment, scaling, and management of containerized applications, enhancing application reliability and scalability. For details, see Ingesting Self-Built Kubernetes Application Logs to LTS.

Configuring ECS Connection to AOM

Node Exporter is an open-source metric collection plug-in from Prometheus. It collects different types of data from target jobs and converts them into the time series data supported by Prometheus. Connect an ECS to AOM. Then you can install Node Exporter and configure collection tasks for the host group. The collected metrics will be stored in the Prometheus instance for ECS for easy management.

Constraints

A host supports only one Node Exporter.

Procedure

1. Log in to the AOM 2.0 console.
2. In the navigation pane, choose Access Center > Access Center. Click Try New Version in the upper right corner of the page.
3. Locate the Elastic Cloud Server (ECS) card under Running environments and click Ingest Metric (AOM) on the card.
4. Set parameters for connecting to the ECS.
   1. Select a Prometheus instance.
      1. Instance Type: Select a Prometheus instance type. Options: Prometheus for ECS and Common Prometheus instance.
      2. Instance Name: Select a Prometheus instance from the drop-down list.

         If no Prometheus instance is available, click Create Instance to create one.

   2. Select a host group.
      In the host group list, select a target host group.

      • If no host group is available, click Create Host Group to create one.
      • You can also perform editing, deletion, and other operations on the host group as needed. For details, see (New) Managing Host Groups.

      Collection configurations are delivered by host group. Therefore, it is easy for you to configure data collection for multiple hosts. When there is a new host, simply add it to a host group and the host will automatically inherit the log ingestion configurations associated with the host group.

   3. Configure the collection.
      Under Configure Collection, set parameters by referring to the following table.

      Table 2 Collection configuration

      Category	Parameter	Description
      Basic Settings	Configuration Name	Name of a custom metric ingestion rule. Enter 1 to 50 characters starting with a letter. Only letters, digits, underscores (_), and hyphens (-) are allowed.
      Metric Collection Rule	Metric Collection Interval (s)	Interval for collecting metrics, in seconds. Options: 10, 30, and 60 (default).
      	Metric Collection Timeout (s)	Timeout period for executing a metric collection task, in seconds. Options: 10, 30, and 60 (default). The timeout period cannot exceed the collection interval.
      	Executor	User who executes the metric ingestion rule, that is, the user of the selected host group. Default: root.
      Other	Custom Dimensions	Dimensions (key-value pairs) added to specify additional metric attributes. You can click Add Dimension to add multiple custom dimensions (key-value pairs). Key: key of the additional attribute of a metric. Enter 1 to 64 characters starting with a letter or underscore (_). Only letters, digits, and underscores are allowed. Value: corresponds to the key of the additional attribute of a metric. Up to 10 dimensions can be added. Example: Set the key to app and value to abc.
      	Import ECS Tags as Dimensions	Whether to import ECS tags as dimensions. Disable: AOM does not write ECS tags (key-value pairs) into metric dimensions. ECS tag changes (such as addition, deletion, and modification) will not be synchronized to metric dimensions. This function is disabled by default. Enable: AOM writes ECS tags (key-value pairs) into metric dimensions. ECS tag changes (such as addition, deletion, and modification) will be synchronized to metric dimensions.

5. After the configuration is complete, click Next. The ECS is then connected.
   After connecting to the ECS, perform the following operations if needed:

   • Go to the Metric Browsing page to analyze metrics. For details, see Observability Metric Browsing.
   • Go to the Access Management page to view, edit, or delete the configured ingestion rule. For details, see Managing Metric and Log Ingestion.

   • Go to the Infrastructure Monitoring > Host Monitoring page to view host monitoring information. For details, see Host Monitoring.