You can use Application Real-Time Monitoring Service (ARMS) to manage ACK Serverless clusters that are deployed across regions in a unified manner. This topic describes how to enable ARMS for an ACK Serverless Basic cluster.
Table of contents
Prerequisites
Step 1: Install the ARMS application monitoring agent
Before you install the ARMS application monitoring agent, check whether your ACK Serverless cluster has ARMS Addon Token. If the cluster has ARMS Addon Token, ARMS performs passwordless authentication. If the cluster does not have ARMS Addon Token, you need to manually specify the AccessKey ID and AccessKey secret to complete authentication.
How do I check whether ARMS Addon Token exists in a cluster?
Log on to the ACK console. In the left-side navigation pane, click Clusters. On the Clusters page, click the name of the cluster to go to the cluster details page.
In the left-side navigation pane, choose
.In the upper part of the page, select kube-system from the Namespace drop-down list and check whether addon.arms.token is displayed on the Secrets page.
Procedure
Complete authorization on the Cloud Resource Access Authorization page.
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, click the name of the cluster that you want to manage and choose in the left-side navigation pane.
On the Add-ons page, click the Logs and Monitoring tab and click Install in the ack-onepilot card.
In the Install ack-onepilot dialog box, configure the parameters and click OK.
If the ACK Serverless cluster does not have ARMS Addon Token, you need to specify the AccessKey ID and AccessKey secret. You can configure other parameters on demand. We recommend that you use the default settings.
Parameter
Description
accessKey
The AccessKey ID of your Alibaba Cloud account. Your account must be authorized to access ARMS.
accessKeySecret
The AccessKey secret of your Alibaba Cloud account.
Step 2: Enable ARMS for a Java application
To enable Application Monitoring when you create an application, perform the following steps:
Log on to the ACK console. In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster that you want to manage, and click Applications in the Actions column.
On the Deployments page, click Create from YAML in the upper-right corner of the page.
On the page that appears, select a template from the Sample Template drop-down list, and add the following
labels
to the spec > template > metadata section in the Template code editor:labels: armsPilotAutoEnable: "on" armsPilotCreateAppName: "<your-deployment-name>" # Replace <your-deployment-name> with the actual application name. armsSecAutoEnable: "on" # If you want to connect the application to Application Security, you must configure this parameter.
NoteFor information about Application Security, see What is Application Security?.
For information about the billing of Application Security, see Billing rules.
The following YAML template shows how to create a Deployment application and enable Application Monitoring for the application:
On the Deployments page, click ARMS Console in the Actions column of the Java application to navigate to the ARMS console and perform service governance.
What to do next
Uninstall ack-onepilot for all applications in the cluster
Log on to the ACK console.
In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster that contains the Java application from which you want to uninstall the ARMS agent, and click Applications in the Actions column.
In the left-side navigation pane, choose
.On the Helm page, find the release named ack-onepilot of the ARMS agent, and click Delete in the Actions column.
In the Delete message, click OK.
Restart the pod of your service.
Uninstall ack-onepilot for an application in the cluster
Log on to the ACK console. In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster that you want to manage, and click Applications in the Actions column.
On the Deployments page, choose in the Actions column of the application that you want to manage.
In the Edit YAML dialog box, delete the
labels
that you added in Step 3: Enable Application Monitoring to monitor a Java application, and then click Update.Restart the pods.
Only the accessKey and accessKeySecret parameters are required. You can configure other parameters on demand. We recommend that you use the default settings. The accessKey parameter specifies the AccessKey ID of your account. Your account must be authorized to access ARMS. The accessKeySecret parameter specifies the AccessKey secret of your account.