Managed Service for Prometheus:Migrate from a self-managed open source Prometheus to Managed Service for Prometheus

Migration steps

1. Connect the ACK container cluster to Managed Service for Prometheus. For more information, see Container Observability.

   Note

   When you connect an ACK cluster, the collection agent for Managed Service for Prometheus (the ack-arms-prometheus component) automatically installs node-exporter. This can cause a port conflict that prevents node-exporter from starting. To resolve this, you can change the default port for node-exporter. In the container cluster, go to Helm under Applications. Find the arms-prometheus application and click Update. Find the `nodeExporter - args - port` parameter and change its value.

2. Configure collection tasks. Managed Service for Prometheus supports multiple configuration methods, such as ServiceMonitor, PodMonitor, and custom collection. For more information, see Manage custom collection rules for container environments.

3. Verify that the collection tasks are running correctly. Log on to the Cloud Monitor console. Click Integration Center, find the container cluster environment, and then click its details. Click Self-Monitoring to view the scrape targets for the environment. Expand a specific scrape job to view the collected metric information.

Migration steps

1. Log on to the Cloud Monitor console. In the Integration Center, select Host Monitor. Follow the on-screen instructions to connect your hosts. This process creates an ECS environment instance and deploys the exporter and collection configuration required for ECS host monitoring.

   Note

   The host monitoring component installs node-exporter and process-exporter by default. To avoid port conflicts, you can set the default ports in the connection configuration. You can also install these exporters as needed during the connection process.

2. Configure custom collection tasks. If you have other exporters deployed on your ECS instances, go to the Integration Center in the Application Real-Time Monitoring Service (ARMS) console. Find Custom Metric Collection and select the ECS (VPC) environment. Configure the exporter's service port, metric collection path, and collection interval. Then, click OK. Repeat these steps to connect multiple exporters.

3. Verify that the collection tasks are running correctly. In the Cloud Monitor console, go to the Integration Center. Find the ECS environment and click its details. Click Self-Monitoring to view the scrape targets for the environment. Expand a specific scrape job to view the collected metric information.

Migration requirements

• Connect your self-managed data center to an Alibaba Cloud VPC using a leased line or a similar method.

• Install exporters on each host in your self-managed data center as needed.

Migration steps

1. Log on to the Cloud Monitor console. In the Integration Center, select Host Monitor (self-service installation + IP domain selection). Follow the on-screen instructions to connect your hosts. This process creates an ECS environment instance and generates the collection configuration for host monitoring.

2. In the Integration Center, connect the monitoring components within the VPC. This allows Managed Service for Prometheus to generate scrape jobs, scrape monitoring data, and create default dashboards and alert rules.

3. [Optional] For custom collection tasks, configure custom collection rules on the corresponding environment instance in the Integration Center.

4. As in Scenario 3: Alibaba Cloud ECS, go to the Integration Center to view the scrape targets.

Prerequisite

You have activated Managed Service for Grafana and created a Grafana workspace.

Migration steps

1. Connect your Managed Service for Prometheus instance to the managed Grafana service. After creating a Grafana workspace, log on to the Alibaba Cloud Grafana console and access the workspace. Click Cloud Service Integration, find the Prometheus instance that you want to integrate, and click Integrations. Follow the prompts. A Prometheus data source is automatically created in the managed Grafana. The data source is named prom-${PrometheusInstanceId}.

2. After the integration is complete, click the public network address for the managed Grafana to log on to the Grafana workspace. When you create a new dashboard, import the JSON file of an existing dashboard. Select the data source that you integrated in the previous step and follow the on-screen instructions.