Managing Prometheus Instances

AOM allows you to create multiple types of Prometheus instances. You can view the names, types, and enterprise projects of Prometheus instances in the instance list and modify and delete them as required.

Creating a Prometheus Instance

Log in to the AOM 2.0 console.
In the navigation pane on the left, choose Prometheus Monitoring > Instances. On the displayed page, click Add Prometheus Instance.

Set an instance name, enterprise project, and instance type.

**Table 1** Parameters for creating a Prometheus instance
Parameter	Description
Instance Name	Prometheus instance name. Enter a maximum of 100 characters and do not start or end with an underscore (_) or hyphen (-). Only letters, digits, underscores, and hyphens are allowed.
Enterprise Project	Enterprise project. If you have selected All for Enterprise Project on the global settings page, select one from the drop-down list here. If you have already selected an enterprise project on the global settings page, this option will be dimmed and cannot be changed.
Instance Type	Type of the Prometheus instance. Options: Prometheus for CCE Prometheus for ECS Prometheus for Cloud Services Common Prometheus Instance Prometheus for Multi-Account Aggregation Select a Prometheus instance type by referring to Table 1. The following instances cannot be directly created: default: Prometheus_AOM_Default is preset. Prometheus for APM: When an application is connected to the APM console, the system automatically creates a Prometheus instance for APM and displays it on the Prometheus Monitoring > Instances page of the AOM console.

Click OK. The Prometheus instance is created.

Then you can perform the operations listed in the following table as required.

**Table 2** Related operations
Sub-Menu	Description
Connecting a CCE Cluster	AOM supports the Prometheus cloud-native monitoring plug-in. You can install the plug-in for CCE clusters through Integration Center to report metrics to the Prometheus instance for CCE. Only Prometheus instances for CCE support this function.
Connecting Middleware to AOM	AOM supports the Prometheus middleware plug-in. You can install the middleware Exporter for VMs through Access Center to report metrics to the Prometheus instance for ECS. Only Prometheus instances for ECS support this function.
Connecting Cloud Services to AOM	You can connect cloud services to AOM through Cloud Service Connection to report metrics to the Prometheus instance for cloud services. Only Prometheus instances for cloud services support this function.
Connecting Accounts	You can connect multiple member accounts within the same organization through Account Access to monitor metrics. Through data multi-write, cross-VPC access can be achieved without exposing the network information about servers. Only Prometheus instances for multi-account aggregation support this function.
Managing Prometheus Instance Metrics	AOM allows you to view Prometheus instance metrics, including new and discarded ones on the Metric Management page. Only the default/common Prometheus instances, and the Prometheus instances for cloud services/ECS/CCE/APM support this function.
Monitoring Prometheus Instance Metrics Through Dashboards	AOM allows you to use preset templates to quickly monitor metrics of Prometheus instance for cloud services and the default Prometheus instance on the Dashboards page. In this way, you can locate problems in a timely manner, improving O&M efficiency. Only the Prometheus instance for cloud services and the default Prometheus instance support this function.
Configuring Data Multi-Write to Dump Metrics to Self-Built Prometheus Instances	AOM supports cross-VPC access through the data multi-write function. Only the default or common Prometheus instance and the Prometheus instances for CCE, cloud service, and ECS are supported.
Setting Metric Storage Duration	AOM allows you to configure the metric storage duration of Prometheus instances. Only the default/common Prometheus instances, and the Prometheus instances for cloud services/ECS/CCE/multi-account aggregation/APM support this function.
Configuring the Remote Read Address to Enable Self-built Prometheus to Read Data from AOM	AOM allows you to check the basic information, call credentials, and service address of a Prometheus instance on the Settings page. Only the default/common Prometheus instances, and the Prometheus instances for cloud services/ECS/CCE/multi-account aggregation/APM support this function.

Managing Prometheus Instances

In the navigation pane on the left, choose Prometheus Monitoring > Instances. In the instance list, view the created Prometheus instances and perform the operations listed in Table 3 if needed.

Figure 1 Managing Prometheus instances

**Table 3** Related operations
Operation	Description
Searching for a Prometheus instance	Enter an instance name in the search box and click .
Filtering and displaying Prometheus instances	Click next to the Instance Type column to filter Prometheus instances.
Refreshing Prometheus instances	Click in the upper right corner of the Prometheus instance list to obtain their latest information in real time.
Checking a Prometheus instance	The Prometheus instance list displays information such as the instance name, instance type, billing mode, and enterprise project in real time. When you have an access code: Click an instance name. On the displayed instance details page, choose Settings and view the basic information and credential of the instance. By default, the AppSecret is hidden. To show it, click . or reflects the status of the AppSecret. In the Grafana Data Source Info area, obtain the Grafana data source configuration code in the private or public network of the desire Prometheus instance. Then click on the right to copy the code to the corresponding file. In the Service Addresses area, obtain the remote read and write configuration code in the private or public network of the desire Prometheus instance. Then click on the right to copy the code to the corresponding file. For details, see Obtaining the Service Address of a Prometheus Instance. When you do not have an access code: Click an instance name. On the displayed instance details page, choose Settings and view the basic information about the instance. The system displays a message indicating that there is no access code. Click Add Access Code. In the displayed dialog box, click OK. Then, choose Settings in the navigation pane of the AOM 2.0 console. On the displayed page, choose Authentication in the navigation pane and manage access codes. For details, see Other Operations.
Modifying a Prometheus instance	Modify a Prometheus instance name: Click in the Operation column that contains the target Prometheus instance. The name of each Prometheus instance in an enterprise project must be unique. (The default and Prometheus for APM instance names cannot be changed.) Modify Prometheus instance configurations: In the Prometheus instance list, click the name of a Prometheus instance for cloud services/CCE/multi-account aggregation and modify the cloud services/CCE clusters/accounts if needed.
Deleting a Prometheus instance	Click in the Operation column that contains the target Prometheus instance. The default and Prometheus for APM instances cannot be deleted. If you delete a Prometheus instance connected to a CCE cluster, cluster metrics cannot be hosted to this instance after it is deleted.
Checking the billing information of a Prometheus instance	In the Prometheus instance list, the Billing Mode column displays the billing mode and creation time of the Prometheus instance. Currently, only pay-per-use billing is supported. If your account is frozen or restricted, you cannot add, delete, or modify Prometheus instances. To continue using your cloud services, top up your account in time. For details, see Arrears.