Metrics used to collect and display statistical indicator of cluster. Apache ShardingSphere supports Prometheus by default. 8.10. Observability 53 Apache ShardingSphere document 8.10.2 Challenges Tracing number of threads and SQL processing information) are exposed to a third‐party application (such as Prometheus) using a standard interface. Administrators can visually monitor the real‐time system sta‐ tus ogging-file-${latest.release.version}.jar │ ├── metrics │ │ └── shardingsphere-agent-metrics-prometheus-${latest.release.version}.jar │ └── tracing │ ├── shardingsphere-agent-tracing-opentelemetry-${latest

Metrics used to collect and display statistical indicator of cluster. Apache ShardingSphere supports Prometheus by default. 8.10. Observability 53 Apache ShardingSphere document 8.10. Observability 54 Apache number of threads and SQL processing information) are exposed to a third‐party application (such as Prometheus) using a standard interface. Administrators can visually monitor the real‐time system sta‐ tus ogging-file-${latest.release.version}.jar │ ├── metrics │ │ └── shardingsphere-agent-metrics-prometheus-${latest.release.version}.jar │ └── tracing │ ├── shardingsphere-agent-tracing-opentelemetry-${latest

Metrics used to collect and display statistical indicator of cluster. Apache ShardingSphere supports Prometheus by default. 3.10. Observability 51 Apache ShardingSphere document, v5.2.0 3.10.2 Challenges number of threads and SQL processing information) are exposed to a third‐party application (such as Prometheus) using a standard interface. Administrators can visually monitor the real‐time system sta‐ tus shardingsphere-agent-logging-base-${latest.release.version}.jar │ ├── shardingsphere-agent-metrics-prometheus-${latest.release.version}.jar │ ├── shardingsphere-agent-tracing-jaeger-${latest.release.version}

Metrics used to collect and display statistical indicator of cluster. Apache ShardingSphere supports Prometheus by default. 3.10. Observability 50 Apache ShardingSphere document, v5.2.1 3.10.2 Challenges number of threads and SQL processing information) are exposed to a third‐party application (such as Prometheus) using a standard interface. Administrators can visually monitor the real‐time system sta‐ tus shardingsphere-agent-logging-base-${latest.release.version}.jar │ ├── shardingsphere-agent-metrics-prometheus-${latest.release.version}.jar │ ├── shardingsphere-agent-tracing-jaeger-${latest.release.version}

可观察性 47 Apache ShardingSphere document Metrics 则用于收集和展示整个集群的统计指标。Apache ShardingSphere 默认提供了对 Prometheus 的 支持。 8.10.2 挑战 Tracing 和 Metrics 需要通过埋点来收集系统信息。大量的埋点使项目核心代码支离破碎，难于维护，且 不易定制化统计指标。 8.10.3 ShardingSphere document 监控仪表盘 将系统静态信息（如应用版本）和动态信息（如线程数、SQL 处理信息）等 Metrics 指标，使用标准接口 方式暴露给第三方应用（如 Prometheus），管理员能够通过可视化的方式监控系统实时状态。 应用性能监控 在 ShardingSphere 中，一条 SQL 语句要经历解析、路由、改写、执行、结果归并等流程才能最终执行完 成，并输出响应。如果 ogging-file-${latest.release.version}.jar │ ├── metrics │ │ └── shardingsphere-agent-metrics-prometheus-${latest.release.version}.jar │ └── tracing │ ├── shardingsphere-agent-tracing-opentelemetry-${latest

可观察性 47 Apache ShardingSphere document Metrics 则用于收集和展示整个集群的统计指标。Apache ShardingSphere 默认提供了对 Prometheus 的 支持。 8.10.2 挑战 Tracing 和 Metrics 需要通过埋点来收集系统信息。大量的埋点使项目核心代码支离破碎，难于维护，且 不易定制化统计指标。 8.10.3 ShardingSphere document 监控仪表盘 将系统静态信息（如应用版本）和动态信息（如线程数、SQL 处理信息）等 Metrics 指标，使用标准接口 方式暴露给第三方应用（如 Prometheus），管理员能够通过可视化的方式监控系统实时状态。 应用性能监控 在 ShardingSphere 中，一条 SQL 语句要经历解析、路由、改写、执行、结果归并等流程才能最终执行完 成，并输出响应。如果 ogging-file-${latest.release.version}.jar │ ├── metrics │ │ └── shardingsphere-agent-metrics-prometheus-${latest.release.version}.jar │ └── tracing │ ├── shardingsphere-agent-tracing-opentelemetry-${latest

Metrics used to collect and display statistical indicator of cluster. Apache ShardingSphere supports Prometheus by default. 4.10.2 Challenges Tracing and metrics need to collect system information through ���shardingsphere− agent − logging − base−{latest.release.version}.jar � ��� shardingsphere‐agent‐ metrics‐prometheus‐latest.release.version.jar� ���shardingsphere − agent − tracing − jaeger−{latest.release.version} configuration file. The plug-ins include Jaeger, opentracing, Zipkin, opentelemetry, logging and Prometheus. Remove the corresponding plug-in in ignoredpluginnames to start the plug-in. ```yaml 4.10.

中。注意这种方式的自动探针不能与 Apache ShardingSphere 插件探针同时使 用。 Metrics 则用于收集和展示整个集群的统计指标。Apache ShardingSphere 默认提供了对 Prometheus 的 支持。 8.10. 可观察性 47 Apache ShardingSphere document 8.10. 可观察性 48 Apache ShardingSphere document 模块为应用提供可观察性的能力，可适用于以下场景： 监控仪表盘 将系统静态信息（如应用版本）和动态信息（如线程数、SQL 处理信息）等 Metrics 指标，使用标准接口 方式暴露给第三方应用（如 Prometheus），管理员能够通过可视化的方式监控系统实时状态。 应用性能监控 在 ShardingSphere 中，一条 SQL 语句要经历解析、路由、改写、执行、结果归并等流程才能最终执行完 成，并输出响应。如果 ogging-file-${latest.release.version}.jar │ ├── metrics │ │ └── shardingsphere-agent-metrics-prometheus-${latest.release.version}.jar │ └── tracing │ ├── shardingsphere-agent-tracing-opentelemetry-${latest

中。注意这种方式的自动探针不能与 Apache ShardingSphere 插件探针同时使 用。 Metrics 则用于收集和展示整个集群的统计指标。Apache ShardingSphere 默认提供了对 Prometheus 的 支持。 3.10. 可观察性 45 Apache ShardingSphere document, v5.2.0 3.10.2 挑战 Tracing 和 Metrics 需要 模块为应用提供可观察性的能力，可适用于以下场景： 监控仪表盘 将系统静态信息（如应用版本）和动态信息（如线程数、SQL 处理信息）等 Metrics 指标，使用标准接口 方式暴露给第三方应用（如 Prometheus），管理员能够通过可视化的方式监控系统实时状态。 应用性能监控 在 ShardingSphere 中，一条 SQL 语句要经历解析、路由、改写、执行、结果归并等流程才能最终执行完 成，并输出响应。如果 shardingsphere-agent-logging-base-${latest.release.version}.jar │ ├── shardingsphere-agent-metrics-prometheus-${latest.release.version}.jar │ ├── shardingsphere-agent-tracing-jaeger-${latest.release.version}

Metrics used to collect and display statistical indicator of cluster. Apache ShardingSphere supports Prometheus by default. 4.10. Observability 65 Apache ShardingSphere document, v5.1.2 4.10.2 Challenges ���shardingsphere− agent − logging − base−{latest.release.version}.jar � ��� shardingsphere‐agent‐ metrics‐prometheus‐latest.release.version.jar� ���shardingsphere − agent − tracing − jaeger−{latest.release.version} 10. Observability 67 Apache ShardingSphere document, v5.1.2 Zipkin, opentelemetry, logging and Prometheus. Remove the corresponding plug-in in ignoredpluginnames to start the plug-in. ```yaml applicationName: