Container Service for Kubernetes:Connect to and configure Managed Service for Prometheus

The Prometheus Monitoring page shows "No related monitoring dashboard found"

This typically means the Prometheus instance lost its connection to the cluster after installation. Reinstall the component first, then check the agent connection if the issue persists.

1. Reinstall the Prometheus monitoring component.

   1. Disable Prometheus monitoring.

   2. After confirming uninstallation is complete, click Install, then click OK in the dialog box.

   3. After installation completes, return to the Prometheus Monitoring page to check whether the issue is resolved. If the issue persists, continue to the next step.

2. Check the Prometheus instance connection.

   1. In the ARMS consoleARMS console left navigation pane, click Integration Management.

   2. On the Integrated Environments tab, check the Container Service list for a container environment with the same name as your cluster.

      • No matching environment found — See Connect using the ARMS or Prometheus console.

      • Matching environment found — Click Configure Agent in the Actions column to open the Configure Agent page and verify that the installed agents are running as expected.

How do I adjust the metric storage duration?

See Adjust metric storage duration.

How do I view the version of the ack-arms-prometheus component?

1. On the ClustersClustersClustersClustersClusters page, click the name of the target cluster. In the left navigation pane, click Add-ons.

2. On the Add-ons page, click the Logs and Monitoring tab and find the ack-arms-prometheus component. The current version is displayed below the component name. If a newer version is available, click Upgrade next to the version number.

   The Upgrade option appears only if the installed version is not the latest.

Why can't I deploy GPU monitoring?

GPU monitoring may fail to deploy if a GPU node has taints. Run the following command to check for taints on the node.

kubectl describe node cn-beijing.47.100.***.***

If the node has custom taints, the output includes entries for them. For example, a taint with key test-key, value test-value, and effect NoSchedule appears as:

Taints: test-key=test-value:NoSchedule

To resolve the issue, use one of the following approaches:

• Remove the taint from the GPU node:

  kubectl taint node cn-beijing.47.100.***.*** test-key=test-value:NoSchedule-

• Add a toleration to the ack-prometheus-gpu-exporter DaemonSet so pods can be scheduled to the node:

  # Edit the ack-prometheus-gpu-exporter DaemonSet
  kubectl edit daemonset -n arms-prom ack-prometheus-gpu-exporter

  Add the following tolerations field at the same level as containers:

  # Add above the containers field, at the same indentation level
  tolerations:
  - key: "test-key"
    operator: "Equal"
    value: "test-value"
    effect: "NoSchedule"
  containers:
   # Other fields omitted

How do I completely and manually delete ARMS-Prometheus?

Deleting only the arms-prom namespace leaves residual configurations that can cause reinstallation to fail. To fully remove all ARMS-Prometheus resources, run the following commands.

• Delete the arms-prom namespace:

  kubectl delete namespace arms-prom

• Delete ClusterRoles:

  kubectl delete ClusterRole arms-kube-state-metrics
  kubectl delete ClusterRole arms-node-exporter
  kubectl delete ClusterRole arms-prom-ack-arms-prometheus-role
  kubectl delete ClusterRole arms-prometheus-oper3
  kubectl delete ClusterRole arms-prometheus-ack-arms-prometheus-role
  kubectl delete ClusterRole arms-pilot-prom-k8s
  kubectl delete ClusterRole gpu-prometheus-exporter
  kubectl delete ClusterRole o11y:addon-controller:role
  kubectl delete ClusterRole arms-aliyunserviceroleforarms-clusterrole

• Delete ClusterRoleBindings:

  kubectl delete ClusterRoleBinding arms-node-exporter
  kubectl delete ClusterRoleBinding arms-prom-ack-arms-prometheus-role-binding
  kubectl delete ClusterRoleBinding arms-prometheus-oper-bind2
  kubectl delete ClusterRoleBinding arms-kube-state-metrics
  kubectl delete ClusterRoleBinding arms-pilot-prom-k8s
  kubectl delete ClusterRoleBinding arms-prometheus-ack-arms-prometheus-role-binding
  kubectl delete ClusterRoleBinding gpu-prometheus-exporter
  kubectl delete ClusterRoleBinding o11y:addon-controller:rolebinding
  kubectl delete ClusterRoleBinding arms-kube-state-metrics-agent
  kubectl delete ClusterRoleBinding arms-node-exporter-agent
  kubectl delete ClusterRoleBinding arms-aliyunserviceroleforarms-clusterrolebinding

• Delete Roles and RoleBindings:

  kubectl delete Role arms-pilot-prom-spec-ns-k8s
  kubectl delete Role arms-pilot-prom-spec-ns-k8s -n kube-system
  kubectl delete RoleBinding arms-pilot-prom-spec-ns-k8s
  kubectl delete RoleBinding arms-pilot-prom-spec-ns-k8s -n kube-system

How do I uninstall Managed Service for Prometheus using Helm?

Use this method if you deployed the service manually with Helm, or if residual resources remain due to environment or Helm version issues.

1. On the ClustersClustersClustersClustersClusters page, click the name of the target cluster. In the left navigation pane, choose Applications > Helm.

2. On the Helm page, find the arms-prometheus component, click Delete in the Actions column, select Clear Release Records, and follow the prompts.

An "xxx in use" error occurs when installing ack-arms-prometheus

1. On the ClustersClustersClustersClustersClusters page, click the name of the target cluster. In the left navigation pane, choose Applications > Helm.

2. On the Helm page, check whether ack-arms-prometheus exists.

   • Found — Delete ack-arms-prometheus from the Helm page, then reinstall it on the Add-ons page. For details, see Manage components.

   • Not found — Residual resources remain from a previous deletion of the ack-arms-prometheus Helm release. Manually delete all ARMS-Prometheus resources, then re-enable Prometheus monitoring.

Installation of ack-arms-prometheus fails after a "Component Not Installed" message

Check each of the following in order:

1. Verify whether ack-arms-prometheus is already installed.

   1. On the ClustersClustersClustersClustersClusters page, click the name of the target cluster. In the left navigation pane, choose Applications > Helm.

   2. On the Helm page, check whether ack-arms-prometheus exists.

      • Found — Delete ack-arms-prometheus from the Helm page, then reinstall it on the Add-ons page. For details, see Manage components.

      • Not found — Manually delete all ARMS-Prometheus resources, then re-enable Prometheus monitoring.

2. Check ack-arms-prometheus logs for errors.

   1. In the cluster details left navigation pane, choose Workloads > Deployments.

   2. At the top of the Deployments page, set Namespace to arms-prom and click arms-prometheus-ack-arms-prometheus.

   3. Click the Logs tab and check for errors.

3. Check whether an error occurred during agent installation.

   1. Log on to the ARMS consoleARMS console. In the left navigation pane, click Integration Management.

   2. On the Integration Management tab, find the target container environment in the Container Service list. In the Actions column, click Configure Agent to open the Configure Agent page.