terrymanu commented on issue #36916:
URL:
https://github.com/apache/shardingsphere/issues/36916#issuecomment-3471244617
Thanks for your suggestion! HikariCP connection pool monitoring is indeed
important for ShardingSphere Proxy's stable operation, and we consider this a
relevant core feature.
Regarding the implementation approach, I recommend collecting HikariCP
metrics through the **ShardingSphere Agent**:
### 1. **Implementation Plan**
- Add a new HikariCP monitoring module in the Agent plugin
- Obtain HikariCP connection pool metrics via JMX/MBean
- Integrate with the existing Prometheus metrics export mechanism
### 2. **Advantages**
- **Non-intrusive**: No modifications to ShardingSphere core code required
- **Pluggable**: Users can optionally enable through the Agent plugin
mechanism
- **Lightweight**: Reuses existing Agent and Prometheus infrastructure
without introducing additional dependencies
- **Universal**: Applicable to various deployment modes
Welcome you to provide code implementation for the Agent plugin.
--
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]
