APM is the abbreviation of Application Performance Monitoring. Currently its core function is the performance diagnosis of distributed system, including call chain demonstration, application topology analysis, etc.

Sharding-Sphere Team work with SkyWalking Team to introduce an automatic monitor agent of Sharding-Sphere to send tracing data of Sharding-Sphere to SkyWalking.


Using SkyWalking

Please refer to SkyWalking Manual

Using OpenTracing

If user want to use other APM systems which support OpenTracing, just use sharding-sphere API to work with those APM systems.

Notices: When using SkyWalking’s OpenTracing monitor agent, disabling the original Sharding-Sphere monitor agent plugin is necessary to avoid conflicting with each other.


Application schema

The application is a SpringBoot application, using Sharding-Sphere to access two databases of ds0 and ds1, each owns two tables in database.

Topology diagram

The topology diagram

Although the user accesses the application once, each database is accessed twice. This is because this visit involves two splitting tables in each database, four tables in total.

Tracking diagram

The topology diagram

You can see SQL routing, execution and final result set merge in this figure.

/SHARDING-SPHERE/ROUTING/: Represents the parsing and routing performance of this SQL.

The parsing and routing node

/SHARDING-SPHERE/EXECUTE/{SQLType}: Represents the overall execution performance of this SQL.

The logical execution node

/SHARDING-SPHERE/EXECUTE/{operation}: Represents the performance of the actual SQL.

The actual access node

/SHARDING-SPHERE/MERGE/: Represents the performance of performing merge results.

The actual access node