Help Center> Application Performance Management> Service Overview> Usage Restrictions
Updated on 2022-07-13 GMT+08:00
View PDF

Usage Restrictions

Linux OSs Supported by ICAgent

ICAgent supports multiple Linux Operating Systems (OSs). When purchasing an Elastic Cloud Server (ECS), select an OS that is listed in Table 1.
Table 1 Supported OSs and versions

OS

Version

SUSE

SUSE Enterprise 11 SP4 64-bit

SUSE Enterprise 12 SP1 64-bit

SUSE Enterprise 12 SP2 64-bit

SUSE Enterprise 12 SP3 64-bit

openSUSE

13.2 64-bit

15.0 64-bit

Currently, syslog logs cannot be collected.

42.2 64-bit

EulerOS

2.2 64-bit

2.3 64-bit

2.5 64-bit

CentOS

6.3 64-bit

6.5 64-bit

6.8 64-bit

6.9 64-bit

6.10 64-bit

7.1 64-bit

7.2 64-bit

7.3 64-bit

7.4 64-bit

7.5 64-bit

7.6 64-bit

7.7 64-bit

7.8 64-bit

7.9 64-bit

8.0 64-bit

8.1 64-bit

8.2 64-bit

Ubuntu

14.04 server 64-bit

16.04 server 64-bit

18.04 server 64-bit

Fedora

24 64-bit

25 64-bit

29 64-bit

Debian

7.5.0 32-bit

7.5.0 64-bit

8.2.0 64-bit

8.8.0 64-bit

9.0.0 64-bit
  • For Linux x86_64 servers, ICAgent supports all the OSs and versions listed in the preceding table.
  • For Linux Arm servers, ICAgent only supports CentOS 7.4 and later versions, and other OSs and versions listed in the preceding table.

Supported Java Types

Currently, APM can connect to Java applications. APM supports multiple mainstream Java frameworks, web servers, communications protocols, and databases. For details, see Table 2.
Table 2 Supported Java types

Type

Name

Version

Tool

JDK

JDK 7 and JDK 8

Communications protocol

HttpClient

Apache HttpClient 3, Apache HttpClient 4, and JDK HttpURLConnection

Java framework

CXF Client

2.6.0–3.2.1

iBATIS

2.3.0 and 2.3.4.726

Jersey

2.0–2.9.1

MyBatis

1.0.0–1.3.1 (MyBatis-Spring) and 3.0.1–3.4.5 (MyBatis 3)

Spring

3.1.x–5.0.x

Spring Boot

1.2.x–1.5.x and 2.0.4–2.0.9

Dubbo

2.5.3–2.6.2 (Dubbo RPC and Dubbo REST) and 2.8.4 (Dubbo RPC and Dubbo REST)

Huawei's Cloud Service Engine (CSE)

1.0.0.B011–1.1.0.B046 (REST over Servlet, REST over Vert.x, and Highway RPC)

gRPC

1.11.x–1.14.x

Database

MySQL

mysql-connector-java 5.1.X

Oracle

ojdbc5, ojdbc6, and ojdbc14

Sybase

2.6.0–3.2.1

MariaDB

1.3.x

VoltDB

6.x–7.x

PostgreSQL

9.0.x, 9.1.x, 9.2.x, 9.3.x, 9.4.x, 42.0.x, and 42.1.x

Web server

Tomcat

6.x, 7.x, and 8.x

Jetty

7.6.x–8.0.0 and 8.1.x–9.x.x

JBoss

NOTE:

When JBoss uses the Java agent probe, special settings are required. For details, see How Do I Connect the JBoss Server in Standalone Mode to APM?

7.0.0–12.0.0

Undertow

1.4.x

Message queue

ActiveMQ

5.6.x–5.15.x

RocketMQ

4.1.x–4.2.x

RabbitMQ

1.3.3 and later (spring-rabbit), 2.7.x (amqp-client), 2.6.0, and 3.6.5

Kafka

0.9.0.1–0.10.0.2

NoSQL

Redis

Jedis 2.0.0–2.9.0

Memcache

2.9.0–2.12.3 (Arcus)

MongoDB

3.0.x–3.6.x

Casandra

2.1.x–3.2.x

ZooKeeper

1.0.x (com.github.adyliu.zkclient) and 0.1.x (com.github.sgroschupf.zkclient)

Elasticsearch

2.4.x and 5.1.x

Rest Client

Common HTTP

2.x, 3.x, 4.x (HttpClient), and all (HttpURLConnection)

Probe Quantity

APM collects performance metrics, including tracing, SLA, SQL statement call, and JVM metrics. The resources consumed for collecting these metrics are closely related to the number of APM probes, number of inter-service calling times, and sampling ratio. To ensure data collection reliability, you are advised to use a maximum of 20 APM probes on a single node.