Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Application Performance Management/ FAQs/ Usage FAQs/ How Does APM Collect Probe Data?

How Does APM Collect Probe Data?

Updated on 2024-03-05 GMT+08:00

Collecting Data

Application Performance Management (APM) collects application data through probes. Probes use the bytecode enhancement technology to trace resources and generate call data. The ICAgent obtains and processes the call data. Then, all the data is reported to and displayed on APM. The procedure is as follows:

Collected Data

APM collects service tracing data, resource information, resource attributes, memory monitoring information, and call request KPI data, but does not collect your personal data. The collected data is used only for APM performance analysis and fault diagnosis, and is not used for any commercial purposes. The following table lists the details.

Data Type

Collected Data

Transmission Mode

Storage Mode

Data Purpose

Storage Period

Tracing data

Tracing span data

Transmission through HTTPS encryption and Access Key ID/Secret Access Key (AK/SK) authentication

Project-based isolated storage

Query and display at the tracing frontend

Configurable (7 days at most). The data will be deleted upon expiration.

Call request KPI data

Call initiator address, receiver address, API, duration, and status

Transmission through HTTPS encryption and AK/SK authentication

Project-based isolated storage

Calculation of transaction call KPI metrics, such as throughput, TP99 latency, average latency, and error calls, drawing of application topologies, and display at the frontend

7 days. The data will be deleted upon expiration.

Resource data

Service type, service name, creation time, deletion time, node address, and service release API

Transmission through HTTPS encryption and AK/SK authentication

Project-based isolated storage

Query and display at the resource library frontend

7 days. The data will be deleted upon expiration.

Resource attributes

System type, system startup event, number of CPUs, service executor, service process ID, service pod ID, CPU label, system version, web framework, JVM version, time zone, system name, collector version, and LastMail URL

Transmission through HTTPS encryption and AK/SK authentication

Project-based isolated storage

Query and display at the resource library frontend

7 days. The data will be deleted upon expiration.

Memory monitoring data

Memory usage, used memory, maximum memory, remaining memory, memory threshold-crossing time, and memory monitoring configurations

Transmission through HTTPS encryption and AK/SK authentication

Project-based isolated storage

Query and display at the resource library frontend

7 days. The data will be deleted upon expiration.

APM Resource Overhead

The CPU usage of each probe is less than 5% and used memory is about 250 MB.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback