Container Service for Kubernetes:Configure Managed Service for Prometheus

1. Log on to the ARMS console. In the left-side navigation pane, choose Alert Management > Notification Objects.

2. On the Notification Objects page, select a notification method and create a notification policy.

3. In the left-side navigation pane of the ARMS console, choose Prometheus Monitoring > Prometheus alert rules.

4. On the Prometheus alert rules page, click Create Prometheus Alert Rule.

   For detailed configuration instructions, see Create a Prometheus alert rule.

Prometheus Monitoring page shows no dashboard

If you see the No related monitoring dashboard found prompt on the Operations > Prometheus Monitoring page after you enable Prometheus monitoring, follow these steps to resolve the issue.

1. Reinstall the Prometheus monitoring component.

   1. Disable Prometheus monitoring.

   2. Reinstall the component:

      1. After you confirm that the component is uninstalled, click Install. In the confirmation dialog box, click OK.

      2. After the installation is complete, return to the Prometheus Monitoring page to check whether the issue is resolved.

         If the issue persists, proceed with the following steps.

2. Check the Prometheus instance integration.

   1. In the left-side navigation pane of the ARMS console, click Integration Management.

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

      • If no such container environment exists, see Integrate a service in the ARMS or Prometheus console.

      • If such a container environment exists, click Settings in the Actions column of the target container environment to go to the Settings page.

        Check whether the installed agent is running as expected.

How to adjust the metric retention period

For more information, see Adjust the retention period of metrics.

How to uninstall by using Helm

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

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

2. On the Helm page, find the ack-arms-prometheus release, click Delete in the Actions column, select Clear Release Records, and then delete the application as prompted.

"xxx in use" error during installation

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

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

   • If it exists, delete ack-arms-prometheus from the Helm page and reinstall it on the Add-ons page. For more information about how to install ack-arms-prometheus, see Manage add-ons.

   • If it does not exist:

     1. The ack-arms-prometheus Helm release may have residual resources. Manually uninstall ARMS Prometheus completely.

     2. Re-enable Prometheus monitoring.

"Component Not Installed" error during installation

• Check whether the ack-arms-prometheus component is installed.

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

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

     • If it exists, delete ack-arms-prometheus from the Helm page and reinstall it on the Add-ons page. For more information about how to install ack-arms-prometheus, see Manage add-ons.

     • If it does not exist:

       1. The ack-arms-prometheus Helm release may have residual resources. Manually uninstall ARMS Prometheus completely.

       2. Re-enable Prometheus monitoring.

• Check the logs of ack-arms-prometheus for errors.

  1. In the left-side navigation pane of the cluster details page, choose Workloads > Deployments.

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

  3. Click the Logs tab to check for errors in the logs.

• Check whether an error occurred during agent installation.

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

  2. On the Integrations tab, check the Container Service list. In the Actions column of the target container environment, click Settings to go to the Settings page.

How to grant monitoring permissions for ACK dedicated clusters

1. On the Clusters page, click the name of the target cluster. In the left-side navigation pane, click Cluster Information.

2. On the Basic Information tab, click the KubernetesWorkerRole-*** link next to Worker RAM Role. On the RAM role page, on the Permission Management tab, click the k8sWorkerRole**** link in the Policies column.

3. On the policy details page, click the Policy Content tab and then click Edit Policy Document.

4. In the script editor, add the following authorization rule to the Statement field and click OK.

   {
       "Version": "1",
       "Statement": [
           {
               "Action": [
                   "arms:Describe*",
                   "arms:List*",
                   "arms:Get*",
                   "arms:Search*",
                   "arms:Check*",
                   "arms:Query*",
                   "arms:ListEnvironments",
                   "arms:DescribeAddonRelease",
                   "arms:InstallAddon",
                   "arms:DeleteAddonRelease",
                   "arms:ListEnvironmentDashboards",
                   "arms:ListAddonReleases",
                   "arms:CreateEnvironment",
                   "arms:UpdateEnvironment",
                   "arms:InitEnvironment",
                   "arms:DescribeEnvironment",
                   "arms:InstallEnvironmentFeature",
                   "arms:ListEnvironmentFeatures",
                   "cms:CreateIntegrationPolicy",
                   "cms:ListAddonReleases",
                   "cms:UpdateAddonRelease",
                   "cms:CreateAddonRelease",
                   "cms:GetPrometheusInstance",
                   "cms:ListIntegrationPolicyStorageRequirements"
               ],
               "Resource": "*",
               "Effect": "Allow"
           }
       ]
   }