Ingesting Other Middleware Metrics to AOM

Constraints

• Maximum data volume reported each time: 5 MB by default. If the data volume exceeds 5 MB, the reporting will fail. To increase the limit, submit a service ticket.
• Collection resource specifications: As the amount of reported metric data increases, the resources (CPU) required by the collector also need to be adjusted. Details:
  • If the data volume reported each time is less than 20 MB, you do not need to adjust the collector resource configuration. Instead, retain default specifications.
  • If the data volume reported each time ranges from 20 MB to 50 MB, submit a service ticket to adjust the CPU limit of the collector to 1 core to ensure that the collection task runs properly.

Prerequisites

• The UniAgent has been installed and is running.
• You have created a common Prometheus instance.

• The new access center does not support Other components. Ensure that you have switched to the old access center.

Procedure

1. Log in to the AOM 2.0 console.
2. In the navigation pane on the left, ingest middleware metrics through either of the following entries:
   • Entry 1: Choose Access Center > Access Center. On the displayed page, click the Othe components card in the Prometheus Middleware panel.
   • Entry 2: Choose Prometheus Monitoring > Instances. Click a Prometheus instance for ECS. On the instance details page, choose Access Center and then click the Other components card.

3. On the displayed page, set parameters by referring to the following table.
   Figure 1 Configuring a collection task
   

   Table 1 Parameters for configuring a collection task

   Operation	Parameter	Description
   Select Instance	Prometheus Instance	Select a common Prometheus instance or Prometheus instance for ECS to store collected data. A collection task is associated with a Prometheus instance to mark and classify collected data. If no Prometheus instance meets your requirements, create a common Prometheus instance. (Currently, Prometheus instances for ECS cannot be created. You can only select the Prometheus instances for ECS created earlier.)
   Set Plug-in	OS	Operating system of the host. Only Linux is supported.
   	Collection Plug-in	The default value is CUSTOM_EXPORTER.
   	Plug-in Version	Select a plug-in version. Plug-in versions that have not been released are dimmed and cannot be selected.
   Set Collection Task	Collection Task Name	Name of a collection task. Enter 1 to 50 characters starting with a letter. Only letters, digits, underscores (_), and hyphens (-) are allowed.
   	Host	Click Add Host. On the Add Host page, select the host for configuring the collection task and installing Exporter. Search for and select a host by the host name, IP address, or Agent status. You can click in the upper right corner to deselect the selected host. Ensure that the UniAgent of the selected host is running. Otherwise, no data can be collected.
   	Plug-in Collection Parameters	Exporter Address: IP address and port number of the host where Exporter is installed. The format is "IP address:Port", for example, 10.0.0.1:9100
   	Metric Dimension	Exporter Name: Enter an Exporter name. Click . In the displayed dialog box, select Built-in or Custom to add a metric dimension. Metric dimension name: Built-in metric dimensions: _app, _comp, and _env are available, which are used to identify applications, components, and environments, respectively. Custom metric dimension: Enter a metric dimension name. Each name can contain 1 to 64 characters. Only letters, digits, and underscores (_) are allowed. Each name must start with a letter or underscore. For a host, each metric dimension name must be unique. Metric dimension value: Enter the value of a metric dimension. This value can be duplicate but cannot be empty. Each value can contain 1 to 128 characters. The following characters are not allowed: &|><$;'!-() Up to 10 dimensions can be added. For example, if the dimension name is label1 and the dimension value is label2, label1:"label2" will be displayed.
   	Advanced Settings	Configure the following parameters: Collection Period (s): O&M data collection period, in seconds. Options: 10s, 30s, and 60s (default). Timeout Period (s): the maximum time allowed for executing a collection task, in seconds. Options: 10s, 30s, and 60s (default). The timeout period cannot exceed the collection period. Executor: user who executes the collection task, that is, the user of the selected host. The default value is root. Currently, only the root user is supported.

4. Click Create.
5. The connected plug-in will be displayed on the Collection Tasks tab page of the plug-in card. Click the plug-in card. On the Collection Tasks tab page, click the target collection task to view its details.