Managing Prometheus Instances

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 Enterprise Project is set to All on the global settings page, select an enterprise project from the drop-down list here.
• If you have already selected an enterprise project on the global settings page, this option will be grayed and cannot be changed.

• To select the newly created enterprise project during the creation of a Prometheus instance, wait for about 10 minutes after the enterprise project is created.

Instance Type

Type of the Prometheus instance. Options:

• Prometheus for CCE
• Common instance
• Prometheus for multi-account aggregation
• Prometheus for multi-account virtual aggregation

Select a Prometheus instance type by referring to Table 1.

The following instances cannot be directly created:

• Common Prometheus instance Prometheus_AOM_Default has been preset on AOM. You cannot create such an instance.
• When an application is connected to the AOM or APM console, the system will automatically create a Prometheus instance for APM and displays it on the Prometheus Monitoring > Instances page of the AOM console. Directly creating a Prometheus instance for APM is no longer supported.
• Currently, Prometheus instances for ECS/cloud services cannot be created. However, you can create common Prometheus instances to implement their functions.

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 created earlier support this function. (Currently, Prometheus instances for ECS cannot be created.)

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 created earlier support this function. (Currently, Prometheus instances for cloud services cannot be created.)

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. Only after creating a Prometheus instance for multi-account aggregation and configuring account access can you go to the account access page. The account access function will be unavailable soon. Please use the new method to ingest metrics.

Managing Prometheus Instance Metrics

AOM allows you to view, add, and discard Prometheus instance metric on the Metric Management page.

Only Prometheus instances for CCE/APM, common Prometheus instances, and previously created Prometheus instances for ECS/cloud services support the preceding functions. (Currently, Prometheus instances for ECS/cloud services cannot be created.)

Configuring Data Multi-Write to Dump Metrics to Self-Built Prometheus Instances

AOM supports cross-VPC access through the data multi-write function.

Only Prometheus instances for CCE/multi-account aggregation, common Prometheus instances, and previously created Prometheus instances for ECS/cloud services support this function.

Setting Metric Storage Duration

AOM allows you to configure the metric storage duration of Prometheus instances.

Only Prometheus instances for CCE/multi-account aggregation/APM, common Prometheus instances, and previously created Prometheus instances for ECS/cloud services support this function.

(Currently, Prometheus instances for ECS/cloud services cannot be created.)

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 Prometheus instances for CCE/multi-account aggregation/multi-account virtual aggregation/APM, common Prometheus instances, and previously created Prometheus instances for ECS and cloud services support this function. (Currently, Prometheus instances for ECS/cloud services cannot be created.)

Searching for a Prometheus instance

Enter a Prometheus instance name in the search box and click .

Viewing a Prometheus instance ID

Hover the mouse pointer over a Prometheus instance name. The Prometheus instance ID and name will then be displayed.

Filtering and displaying Prometheus instances

You can filter Prometheus instances by instance name, instance type, or instance ID in the search box.

Refreshing Prometheus instances

Click in the upper right corner of the Prometheus instance list to obtain their latest information in real time.

Managing tags

Move the cursor to in the Tag column to manage the tags of the Prometheus instance.

• Adding a tag: Click Edit Tag. In the displayed dialog box, click Add, enter a tag key and value, and click OK.
• Deleting a tag: Click Edit Tag. In the displayed dialog box, click Delete to delete a tag.

Checking a Prometheus instance

The Prometheus instance list displays information such as the Prometheus instance name/ID, 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 desired 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 desired 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:
  1. 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.
  2. Click Add Access Code. In the displayed dialog box, click OK.

  Then choose Settings > Global Settings in the navigation pane of the AOM console. On the displayed page, choose Authentication in the navigation pane and manage access codes. For details, see Other Operations.

Editing a Prometheus instance

Modify a Prometheus instance name:

Locate the Prometheus instance to be modified and click Edit in the Operation column. Each Prometheus instance name must be unique.

Deleting a Prometheus instance

Locate the target Prometheus instance and click Delete in the Operation column. In the displayed dialog box, enter DELETE or click Auto Enter and then click OK.

• Prometheus instances for APM 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.