76 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 APM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Agent Integration operating and controlling the system through the UI, further improving the support for tracing and APM. 3.4.3 Goal For the governance function, the goals are as follows: • support Zookeeper/etcd, manage the features of the observability: • APM Integration APM Integration Background APM is the abbreviation for application performance monitoring. Currently, main APM functions lie in the performance diagnosis

. 63 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Tracing . them. Tracking, metrics and logging are important ways to obtain observable data of system status. APM (application performance monitoring) is to monitor and diagnose the performance of the system by collecting ShardingSphere is not responsible for gathering, storing and demonstrating APM data, but pro‐ vides the necessary information for the APM. In other words, Apache ShardingSphere is only respon‐ sible for generating

55 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 APM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Agent Integration operating and controlling the system through the UI, further improving the support for tracing and APM. 4.5.3 Goal For the governance function, the goals are as follows: • support Zookeeper/etcd, manage the features of the observability: • APM Integration APM Integration Background APM is the abbreviation for application performance monitoring. Currently, main APM functions lie in the performance diagnosis

. 66 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Tracing . them. Tracking, metrics and logging are important ways to obtain observable data of system status. APM (application performance monitoring) is to monitor and diagnose the performance of the system by collecting ShardingSphere is not responsible for gathering, storing and demonstrating APM data, but pro‐ vides the necessary information for the APM. In other words, Apache ShardingSphere is only respon‐ sible for generating

control plane Configuration center Service center Governance Web Console Monitoring Zipkin Huawei APM Prometheus Grafana Kubernetes Java chassis Service Go chassis Service VM Bare metal CCE ServiceStage configuration center). • Interconnect Mesher with APM for collecting logs. • Interconnect Mesher with APM for collecting metrics. • Interconnect Mesher with APM for tracing call chains. • Notify the user

. 53 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Tracing . them. Tracking, metrics and logging are important ways to obtain observable data of system status. APM (application performance monitoring) is to monitor and diagnose the performance of the system by collecting ShardingSphere is not responsible for gathering, storing and demonstrating APM data, but pro‐ vides the necessary information for the APM. In other words, Apache ShardingSphere is only respon‐ sible for generating

. 52 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Tracing . them. Tracking, metrics and logging are important ways to obtain observable data of system status. APM (application performance monitoring) is to monitor and diagnose the performance of the system by collecting ShardingSphere is not responsible for gathering, storing and demonstrating APM data, but pro‐ vides the necessary information for the APM. In other words, Apache ShardingSphere is only respon‐ sible for generating

. 56 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Tracing . them. Tracking, metrics and logging are important ways to obtain observable data of system status. APM (application performance monitoring) is to monitor and diagnose the performance of the system by collecting ShardingSphere is not responsible for gathering, storing and demonstrating APM data, but pro‐ vides the necessary information for the APM. In other words, Apache ShardingSphere is only respon‐ sible for generating

'Elastic stuff here '================================ !include !include apm/apm.puml> !include !include !include !include skinparam agentBackgroundColor White APM(apm) APP_SEARCH(app_search) BEATS(beats) CLOUD(cloud) CLOUD_IN_KUBERNETES(cloud_in_kubernetes) CODE_SEARCH(code_search)

'Elastic stuff here '================================ !include !include apm/apm.puml> !include !include !include !include skinparam agentBackgroundColor White APM(apm) APP_SEARCH(app_search) BEATS(beats) CLOUD(cloud) CLOUD_IN_KUBERNETES(cloud_in_kubernetes) CODE_SEARCH(code_search)