Download Apache ShardingSphere from GitHub,Then compile.
git clone --depth 1 https://github.com/apache/shardingsphere.git
cd shardingsphere
mvn clean install -DskipITs -DskipTests -Prelease
Agent artifact is distribution/agent/target/apache-shardingsphere-${latest.release.version}-shardingsphere-agent-bin.tar.gz
Create agent directory, and unzip agent distribution package to the directory.
mkdir agent
tar -zxvf apache-shardingsphere-${latest.release.version}-shardingsphere-agent-bin.tar.gz -C agent
cd agent
tree
├── LICENSE
├── NOTICE
├── conf
│ └── agent.yaml
├── plugins
│ ├── lib
│ │ ├── shardingsphere-agent-metrics-core-${latest.release.version}.jar
│ │ └── shardingsphere-agent-plugin-core-${latest.release.version}.jar
│ ├── logging
│ │ └── shardingsphere-agent-logging-file-${latest.release.version}.jar
│ ├── metrics
│ │ └── shardingsphere-agent-metrics-prometheus-${latest.release.version}.jar
│ └── tracing
│ ├── shardingsphere-agent-tracing-opentelemetry-${latest.release.version}.jar
└── shardingsphere-agent-${latest.release.version}.jar
conf/agent.yaml
is used to manage agent configuration.
Built-in plugins include File, Prometheus, OpenTelemetry.
plugins:
# logging:
# File:
# props:
# level: "INFO"
# metrics:
# Prometheus:
# host: "localhost"
# port: 9090
# props:
# jvm-information-collector-enabled: "true"
# tracing:
# OpenTelemetry:
# props:
# otel.service.name: "shardingsphere"
# otel.traces.exporter: "jaeger"
# otel.exporter.otlp.traces.endpoint: "http://localhost:14250"
# otel.traces.sampler: "always_on"
Currently, the File plugin only outputs the time-consuming log output of building metadata, and has no other log output for the time being.
Used for exposure monitoring metrics.
Name | Description |
---|---|
host | host IP |
port | port |
jvm-information-collector-enabled | whether to collect JVM indicator information |
OpenTelemetry can export tracing data to Jaeger, Zipkin.
Name | Description |
---|---|
otel.service.name | service name |
otel.traces.exporter | traces exporter |
otel.exporter.otlp.traces.endpoint | traces endpoint |
otel.traces.sampler | traces sampler |
Parameter reference OpenTelemetry SDK Autoconfigure
SpringBoot
project ready to integrate ShardingSphere-JDBC
, test-project.jarjava -javaagent:/agent/shardingsphere-agent-${latest.release.version}.jar -jar test-project.jar
ShardingSphere Agent has a Dockerfile
available for easy distribution. You can execute the following command to build a Docker Image,
git clone git@github.com:apache/shardingsphere.git
cd ./shardingsphere/
./mvnw -am -pl distribution/agent -Prelease,docker -T1C -DskipTests clean package
If you add the following statement in your custom Dockerfile
, it will copy the ShardingSphere Agent directory to /shardingsphere-agent/
.
COPY --from=apache/shardingsphere-agent:latest /usr/agent/ /shardingsphere-agent/
ShardingSphere Agent has a nightly built Docker Image at https://github.com/apache/shardingsphere/pkgs/container/shardingsphere-agent .
If you add the following statement in your custom Dockerfile
, it will copy the ShardingSphere Agent directory to /shardingsphere-agent/
.
COPY --from=ghcr.io/apache/shardingsphere-agent:latest /usr/agent/ /shardingsphere-agent/
Introduce a typical scenario,
docker network create example-net
docker run --rm -d \
--name jaeger \
-e COLLECTOR_ZIPKIN_HOST_PORT=:9411 \
-p 16686:16686 \
-p 4317:4317 \
-p 4318:4318 \
-p 9411:9411 \
--network example-net \
jaegertracing/all-in-one:1.60.0
./custom-agent.yaml
contains the configuration of ShardingSphere Agent, and the content may be as follows,plugins:
tracing:
OpenTelemetry:
props:
otel.service.name: "example"
otel.exporter.otlp.traces.endpoint: "http://jaeger:4318"
./target/example.jar
is an Uber JAR of Spring Boot that will use ShardingSphere Agent,
you can use the ShardingSphere Agent in the nightly built Docker Image for a JAR like example.jar
through a Dockerfile
like the following.FROM ghcr.io/apache/shardingsphere-agent:latest
COPY ./target/example.jar /app.jar
COPY ./custom-agent.yaml /usr/agent/conf/agent.yaml
ENTRYPOINT ["java","-javaagent:/usr/agent/shardingsphere-agent-5.5.1-SNAPSHOT.jar","-jar","/app.jar "]
If you build the Docker Image of apache/shardingsphere-agent:latest
locally, the Dockerfile
may be as follows,
FROM apache/shardingsphere-agent:latest
COPY ./target/example.jar /app.jar
COPY ./custom-agent.yaml /usr/agent/conf/agent.yaml
ENTRYPOINT ["java","-javaagent:/usr/agent/shardingsphere-agent-5.5.1-SNAPSHOT.jar","-jar","/app.jar"]
docker build -t example/gs-spring-boot-docker:latest .
docker run --network example-net example/gs-spring-boot-docker:latest
Name | Type | Description |
---|---|---|
build_info | GAUGE | Build information |
parsed_sql_total | COUNTER | Total count of parsed by type (INSERT, UPDATE, DELETE, SELECT, DDL, DCL, DAL, TCL, RQL, RDL, RAL, RUL) |
routed_sql_total | COUNTER | Total count of routed by type (INSERT, UPDATE, DELETE, SELECT) |
routed_result_total | COUNTER | Total count of routed result (data source routed, table routed) |
jdbc_state | GAUGE | Status information of ShardingSphere-JDBC. 0 is OK; 1 is CIRCUIT BREAK; 2 is LOCK |
jdbc_meta_data_info | GAUGE | Meta data information of ShardingSphere-JDBC |
jdbc_statement_execute_total | GAUGE | Total number of statements executed |
jdbc_statement_execute_errors_total | GAUGE | Total number of statement execution errors |
jdbc_statement_execute_latency_millis | HISTOGRAM | Statement execution latency |
jdbc_transactions_total | GAUGE | Total number of transactions, classify by commit and rollback |