Application Real-Time Monitoring Service:Monitor Java applications in an ACK cluster

Workflow

1. Install an agent for the application.

   1. Install the ack-onepilot component: ack-onepilot is a system component of ACK that connects Java or Go applications deployed in ACK to ARMS.

   2. Update the YAML file: Add labels to the application's YAML file to enable monitoring and set its display name in ARMS.

2. View monitoring data.

3. Configure alerts.

Prerequisites

• ACK:

  • A Kubernetes cluster is created. For more information, see Create an ACK managed cluster.

  • A Java application:

    • For JDK version requirements, see Java components and frameworks supported by Application Monitoring.

    • The maximum heap memory of the process must be greater than 256 MB.

    If you do not have a Java application, you can use the following sample YAML to create one. For more information, see Create a stateless workload (Deployment).

    Note

    The sample YAML creates the following resources:

    • A namespace named arms-demo. All subsequent resources are created in this namespace.

    • Two stateless workloads: arms-springboot-demo and arms-springboot-demo-subcomponent.

    • A Service named arms-demo-component.

    • A database named arms-demo-mysql.

    Expand to view the complete sample YAML file (Java)

    apiVersion: v1
    kind: Namespace
    metadata:
      name: arms-demo
    ---
    apiVersion: apps/v1 # for versions before 1.8.0 use apps/v1beta1
    kind: Deployment
    metadata:
      name: arms-springboot-demo
      namespace: arms-demo
      labels:
        app: arms-springboot-demo
    spec:
      replicas: 2
      selector:
        matchLabels:
          app: arms-springboot-demo
      template:
        metadata:
          labels:
            app: arms-springboot-demo
        spec:
          containers:
            - resources:
                limits:
                  cpu: 0.5
              image: registry.cn-hangzhou.aliyuncs.com/arms-docker-repo/arms-springboot-demo:v0.1
              imagePullPolicy: Always
              name: arms-springboot-demo
              env:
                - name: SELF_INVOKE_SWITCH
                  value: "true"
                - name: COMPONENT_HOST
                  value: "arms-demo-component"
                - name: COMPONENT_PORT
                  value: "6666"
                - name: MYSQL_SERVICE_HOST
                  value: "arms-demo-mysql"
                - name: MYSQL_SERVICE_PORT
                  value: "3306"
    ---
    apiVersion: apps/v1 
    kind: Deployment
    metadata:
      name: arms-springboot-demo-subcomponent
      namespace: arms-demo
      labels:
        app: arms-springboot-demo-subcomponent
    spec:
      replicas: 2
      selector:
        matchLabels:
          app: arms-springboot-demo-subcomponent
      template:
        metadata:
          labels:
            app: arms-springboot-demo-subcomponent
        spec:
          containers:
            - resources:
                limits:
                  cpu: 0.5
              image: registry.cn-hangzhou.aliyuncs.com/arms-docker-repo/arms-springboot-demo:v0.1
              imagePullPolicy: Always
              name: arms-springboot-demo-subcomponent
              env:
                - name: SELF_INVOKE_SWITCH
                  value: "false"
                - name: MYSQL_SERVICE_HOST
                  value: "arms-demo-mysql"
                - name: MYSQL_SERVICE_PORT
                  value: "3306"
    ---
    apiVersion: v1
    kind: Service
    metadata:
      labels:
        name: arms-demo-component
      name: arms-demo-component
      namespace: arms-demo
    spec:
      ports:
        # the port that this service should serve on
        - name: arms-demo-component-svc
          port: 6666
          targetPort: 8888
      # label keys and values that must match in order to receive traffic for this service
      selector:
        app: arms-springboot-demo-subcomponent
    ---
    apiVersion: apps/v1 # for versions before 1.8.0 use apps/v1beta1
    kind: Deployment
    metadata:
      name: arms-demo-mysql
      namespace: arms-demo
      labels:
        app: mysql
    spec:
      replicas: 1
      selector:
        matchLabels:
          app: mysql
      template:
        metadata:
          labels:
            app: mysql
        spec:
          containers:
            - resources:
                limits:
                  cpu: 0.5
              image: registry.cn-hangzhou.aliyuncs.com/arms-docker-repo/arms-demo-mysql:v0.1
              name: mysql
              ports:
                - containerPort: 3306
                  name: mysql
    ---
    apiVersion: v1
    kind: Service
    metadata:
      labels:
        name: mysql
      name: arms-demo-mysql
      namespace: arms-demo
    spec:
      ports:
        # the port that this service should serve on
        - name: arms-mysql-svc
          port: 3306
          targetPort: 3306
      # label keys and values that must match in order to receive traffic for this service
      selector:
        app: mysql
    ---

• ARMS:

  A paid edition of Application Monitoring is activated.

  Unused quota does not carry over to the next month. If you exceed the free quota in the current month, you are charged based on the amount of data written. For more information, see Billing.

Install the agent

View monitoring details

Configure alerts

Create alert rules for specific applications. When an alert rule is triggered, the system sends notifications to the specified contacts or DingTalk groups, so you can take action. For more information, see Application Monitoring alert rules.

Example alert rule configuration: For the alert objects, select the arms-k8s-demo and arms-k8s-demo-subcomponent applications. For the metric type, select Statistics on services provided by applications. In the filter conditions, set both API Name and API Call Type to All. The trigger mode is Single Condition. The alert is triggered when the average response time over the last 5 minutes is greater than or equal to the corresponding threshold. The multi-level thresholds are set to P1:critical 6000 ms, P2:error 4000 ms, and P4:page 2500 ms.

Clean up resources

After you complete this tutorial:

• If you want to continue monitoring the application, ensure your account has a sufficient balance.

• If you no longer need to monitor the application, uninstall the agent. For more information, see Uninstall the agent in a Kubernetes environment.

References

• ARMS supports multiple trace sampling modes. You can select a suitable mode based on your use case to obtain the desired trace data at a lower cost. For more information, see Select a trace sampling mode (agent version 3.2.8 or later).

• Application Monitoring lets you correlate TraceIDs in business logs. When an application issue occurs, you can use the TraceID to quickly find the relevant business logs for troubleshooting and resolution. For more information, see Correlate TraceIDs with business logs for Java applications.

• If your online application experiences high CPU or memory usage or a large number of slow calls, you can use the flame graphs generated by the continuous profiling feature in ARMS to identify the root cause. For more information, see Continuous profiling for Java applications.

• Alibaba Cloud Managed Service for Prometheus is integrated with the ARMS Application Monitoring data source by default. You can directly obtain Application Monitoring data, view pre-built Application Monitoring dashboards, and perform custom development in Managed Service for Prometheus. For more information, see Obtain ARMS Application Monitoring data by using Managed Service for Prometheus.