56 Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 9 User Manual Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Impact on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Limitations . . . . . . . Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 9.2.8 Logging Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 Background . .

53 Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 4 User Manual Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Impact on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Limitations . . . . . . . is an open source ecosystem that allows you to transform any database into a distributed database system. The project includes a JDBC and a Proxy, and its core adopts a micro‐ kernel and pluggable architecture

56 Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 8.11 SQL Federation Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Impact on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Limitations . . . . . . . Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 9.2.8 Logging Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Background . .

52 Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 4 User Manual Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Impact on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Limitations . . . . . . . Introduction Apache ShardingSphere is an ecosystem to transform any database into a distributed database system, and enhance it with sharding, elastic scaling, encryption features & more. The project is committed

Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 5.2.4 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 To distinguish The applications and databases that use Database Mesh to visit databases will form a large grid system, where they just need to be put into the right positions accordingly. They are all governed by the registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture to the most applicable one to their needs to

The applications and databases that use Database Mesh to visit databases will form a large grid system, where they just need to be put into the right positions accordingly. They are all governed by the registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture to the most applicable one to their needs to registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture to the most applicable one to their needs to

reasonably making full use of the computation and storage capacity of existed database in distributed system, rather than a totally new database. As the cornerstone of enterprises, relational database still database. The application and database that use Database Mesh to visit database will form a large grid system, where they just need to be put into the right position accordingly. They are all gov‐ erned by same registry center, ShardingSphere can build an application system applicable to all kinds of scenarios. Architects can adjust the system architecture to the most applicable one to current business more

The applications and databases that use Database Mesh to visit databases will form a large grid system, where they just need to be put into the right positions accordingly. They are all governed by the registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture to the most applicable one to their needs to registry center, ShardingSphere can build an application system that is applicable to all kinds of scenarios. Ar‐ chitects can adjust the system architecture to the most applicable one to their needs to

50 Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 8.11 联邦查询 . 系统的全新挑战。登录到具体服务器的点对点运维方式，无法适用于面向大量分布式服务器的场景。通 过对可系统观察性数据的遥测是分布式系统推荐的运维方式。Tracing（链路跟踪）、Metrics（指标监控） 和 Logging （日志）是系统运行状况的可观察性数据重要的获取手段。 APM（应用性能监控）是通过对系统可观察性数据进行采集、存储和分析，进行系统的性能监控与诊断， 主要功能包括性能指标监控、调用链分析，应用拓扑图等。 括调用链展示，应用拓扑分 析等。 Tracing 链路跟踪，通过探针收集调用链数据，并发送到第三方 APM 系统。 Metrics 系统统计指标，通过探针收集，供第三方应用展示。 Logging 日志，通过 Agent 能够方便的扩展日志内容，为分析系统运行状态提供更多信息。 8.11 联邦查询 8.11.1 背景 当用户使用数据分片对海量数据进行水平拆分时，虽然能够有效解决数据库性能瓶颈，但业务上也因此

50 Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9 用户手册 51 9 系统的全新挑战。登录到具体服务器的点对点运维方式，无法适用于面向大量分布式服务器的场景。通 过对可系统观察性数据的遥测是分布式系统推荐的运维方式。Tracing（链路跟踪）、Metrics（指标监控） 和 Logging （日志）是系统运行状况的可观察性数据重要的获取手段。 APM（应用性能监控）是通过对系统可观察性数据进行采集、存储和分析，进行系统的性能监控与诊断， 主要功能包括性能指标监控、调用链分析，应用拓扑图等。 ShardingSphere document Tracing 链路跟踪，通过探针收集调用链数据，并发送到第三方 APM 系统。 Metrics 系统统计指标，通过探针收集，供第三方应用展示。 Logging 日志，通过 Agent 能够方便的扩展日志内容，为分析系统运行状态提供更多信息。 8.10. 可观察性 50 9 用户手册 本章节面向 Apache ShardingSphere 的用户，详细阐述项目的使用说明。