wsm12138 opened a new issue, #22550:
URL: https://github.com/apache/shardingsphere/issues/22550
## Bug Report
### Which version of ShardingSphere did you use?
7e6d00dbfab5f016fae7736f805c34df469a2907
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC or ShardingSphere-Proxy
### Expected behavior
ShardingSphere-JDBC & ShardingSphere-Proxy have same behave.
### Actual behavior
```
[root@localhost 1130]# cat agent/conf/agent.yaml | grep -v ^#
plugins:
metrics:
Prometheus:
host: "localhost"
port: 9999
props:
jvm-information-collector-enabled: "true"
```
Use same `agent.yaml` ，proxy can show metrics，but ss-jdbc can't.
### Reason analyze (If you can)
If i want ss-jdbc + agent have metric,i must start `loggin`.
```
plugins:
logging:
BaseLogging:
props:
level: "INFO"
metrics:
Prometheus:
host: "localhost"
port: 9999
props:
jvm-information-collector-enabled: "true"
```
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
### Example codes for reproduce this issue (such as a github link).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
[email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
