No monitoring data for an application in an ACK cluster after installing an agent - Application Real-Time Monitoring Service

Possible causes

Application monitoring is paused.
The agent in the application's pod failed to load correctly.

Solution

Step 1: Check application monitoring status

Log on to the ARMS console. In the left-side navigation pane, choose Application Monitoring > Application List.
On the Application List page, select your region at the top and then click the name of your application.

If you cannot find your application, proceed to Step 2.
For the new console: In the top navigation bar, choose Application Settings > Custom Configuration. In the Probe Switch Settings section, check the status of the Pause Application Monitoring switch.
- If the Pause Application Monitoring switch is on, turn it off and click Save.
- If the Pause Application Monitoring switch is off, proceed to Step 2.
For the old console: In the left-side navigation pane, click Application Settings, and then click the Custom Configuration tab. In the Agent Switch Settings section, check if the Agent Master Switch is on.
- If the Agent Master Switch is off, turn it on and click Save at the bottom of the page.
- If the Agent Master Switch is on, proceed to Step 2.

Step 2: Verify agent loading

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 Workloads > Pods.
On the Pods page, select your application's namespace. Find the target pod and click Edit YAML in the Actions column.

In the Edit YAML dialog box, check if the YAML file contains initContainers.

state:
          running:
            startedAt: '2023-01-13T08:50:46Z'
  hostIP: xxx.xxx.xx.196
  initContainerStatuses:
    - containerID: >-
        containerd://5d6cff441916ea146f6c9568e86e749817a64f212405349b5edc580991fb3195
      image: >-
        registry-vpc.cn-hangzhou.aliyuncs.com/ack-onepilot/ack-onepilot-init:3.0.6
      imageID: >-
        registry-vpc.cn-hangzhou.aliyuncs.com/ack-onepilot/ack-onepilot-init@sha256:93fe036b4c3dda4d4db3bc90de1e00972199a371ada31d1818b3395ecae8a145
      lastState: {}
      name: one-pilot-initcontainer
      ready: true
      restartCount: 0
      state:
        terminated:
          containerID: >-
            containerd://5d6cff441916ea146f6c9568e86e749817a64f212405349b5edc580991fb3195
          exitCode: 0
          finishedAt: '2023-01-13T08:50:45Z'
          reason: Completed
          startedAt: '2023-01-13T08:50:31Z'
  phase: Running
  podIP: xxx.xxx.xx.241
  podIPs:
    - ip: xxx.xxx.xx.241
  qosClass: Guaranteed
  startTime: '2023-01-13T08:50:30Z'

If it does not exist, the one-pilot-initcontainer has not been injected. Proceed to Step 5.
If it exists, the one-pilot-initcontainer has been injected. Proceed to Step 8.

On the Workloads > Pods page, select the ack-onepilot namespace. Verify that a pod with the prefix ack-onepilot exists and that all ack-onepilot pods have completed their rolling updates.
- If a pod with the prefix exists, proceed to Step 6.
- If a pod with the prefix does not exist, install ack-onepilot from the application marketplace. For instructions, see How to uninstall arms-pilot and install ack-onepilot.
On the Workloads page, go to the Deployments or StatefulSets page. Find your application, and in the Actions column, choose > Edit YAML. In the Edit YAML dialog box, check for the following labels under spec.template.metadata.
```
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.
```
- If the labels exist, proceed to Step 7.
- If the labels do not exist, add them under the spec.template.metadata path in the Edit YAML dialog box and click Update.
On the Workloads > Pods page, select the ack-onepilot namespace. Find the pod with the ack-onepilot prefix, and in the Actions column, choose More > Logs. Check the logs for an STS error, indicated by the message "Message":"STS error".
- If an STS error is reported, authorize the application's cluster and restart the application pod. For instructions, see Authorize Container Service for Kubernetes.
- If no STS error is reported, submit a ticket.
On the Workloads > Pods page, find the target pod and click Edit YAML in the Actions column. In the Edit YAML dialog box, check if the YAML file contains the following javaagent parameter.
```
-javaagent:/home/admin/.opt/ArmsAgent/aliyun-java-agent.jar
```
Note
If you use an agent version earlier than 2.7.3.5, replace aliyun-java-agent.jar with arms-bootstrap-1.7.0-SNAPSHOT.jar. We recommend upgrading the agent to the latest version.
- If available, on the Pod page, click Terminal on the right side to open the Command Line page, run the following command to check for .log files, and then submit a ticket.
```
cd /home/admin/.opt/ArmsAgent/logs
```
- If the parameter does not exist, submit a ticket.

References

Network configuration for Java application monitoring