All Products
Search

This Product

    Application Real-Time Monitoring Service:FAQs about ARMS agent installation

    Document Center

    Application Real-Time Monitoring Service:FAQs about ARMS agent installation

    Last Updated:Feb 12, 2025

    How do I view the logs of the ARMS agent?

    • By default, logs are located in ${agent root directory}/logs/${pid}_${ip}.log.

      ${agent root directory} refers to the agent directory, which depends on how the agent was installed.

      • If the agent was installed in containers, Enterprise Distributed Application Service (EDAS), or Enterprise Distributed Application Service, then ${agent root directory} is /home/admin/.opt/ArmsAgent/ or /home/admin/.opt/AliyunJavaAgent.

      • If the agent was manually installed, then ${agent root directory} refers to the directory where the agent was downloaded and decompressed.

      • If you are not sure how the agent was installed, you can run the ps ef | grep java command to view the startup command of the process, where the agent directory is specified by the -javaagent parameter. Assume that the startup command is -javaagent:/home/zhangsan/agent/arms-bootstrap-1.7.0-SNAPSHOT.jar is seen; so the agent directory is a /home/zhangsan/agent.

    • If you have manually modified the startup parameter -DJM. LOG.PATH=xxx, then logs are located in ${JM.LOG.PATH}/${pid}_${ip}.log.

    Why did the ARMS agent have no data?

    1. Determine if the agent started successfully.

      1. Check whether the standard output logs contain keywords indicating that the agent was successfully loaded while starting the application.

        The standard output logs of the ARMS agent v3.x contains (AliyunJavaAgentBootstrap) arms agent start cost when the agent is mounted.

        The standard output logs of the ARMS agent v4.x contains Aliyun Java Agent start cost when the agent is mounted.

        If no such logs exist, it indicates that the agent is not mounted or the precheck failed. In this case, likewise, log information (such as Aliyun Java Agent requires minimal memory of 200M) illustrates the fact.

      2. Check whether an exception has occurred in the startup logs. If the exception java.security.NoSuchAlgorithmException: DES KeyGenerator not available has occurred, upgrade the agent to 4.x. If not, submit a ticket.

        Note

        For information about the location of agent logs, see How do I view the logs of the ARMS agent?

    2. If the agent started successfully, perform the following steps to continue troubleshooting.

      1. Search for the regionId keyword in the agent logs to determine the region where the agent reports data. Check whether you have selected the correct region.

      2. Check whether the agent has reported any network connectivity-related errors. If yes, we recommend that you refer to the Network configurations required by the ARMS agent for Java topic to resolve the errors.

      3. Check whether the application has traffic.

    1. If the problem persists, submit a ticket.

    Does ARMS support specifying a uniform agent version for the entire Kubernetes cluster, rather than specifying an agent version for individual Deployments?

    Yes. Submit a ticket or contact technical support to specify a uniform agent version for the entire Kubernetes cluster.

    Why does mounting the ARMS agent after the Pinpoint agent result in no data?

    • The ARMS agent v3.x is developed based on the Pinpoint Agent. You can only install either the ARMS agent v3.x or the Pinpoint Agent.

    • The ARMS agent v4.x is developed based on the OpenTelemetry Java agent, which allows it to be mounted alongside the Pinpoint agent. However, compatibility is not guaranteed when both agents are mounted simultaneously.

    How do I resolve the java.lang.NoSuchMethodError after ARMS is connected: 'org.springframework.http.HttpStatus error?

    For an ARMS agent earlier than v3.2.0, if you install an ARMS agent for the application from EDAS and enable the -Dedas.scg.enable feature, com.navercorp.pinpoint.plugin.reactive.filter.AccessLogFilte will be automatically added to the filter chain. The error occurred because the filter is not suitable for spring boot3.. The issue has been fixed in the ARMS agent v3.2.0 and later.

    What is "logContent rate limit count" in the logs?

    This message indicates that the agent has been rate-limited due to excessive log output. Rate limiting is implemented to prevent the application performance from being impacted by too many logs. It does not indicate any malfunction or issue with the agent.