You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CzyerChen
changed the title
[Bug] Add URLParser for Derby/Sybase/SQLite/DB2/OceanBase
[Feature] Add URLParser for Derby/Sybase/SQLite/DB2/OceanBase
May 10, 2024
Can we make sure the only gap for tracing these databases JDBC access are about this?
Because AFAIK, if we don't add instrument for driver explicitly, the connection info is still missing.
Can we make sure the only gap for tracing these databases JDBC access are about this?
Because AFAIK, if we don't add instrument for driver explicitly, the connection info is still missing.
None of these databases have plugins to track SQL statements now, and adding these URLParsers can make connection pools report pool metrics of these databases successfully.
Meanwhile, for database connection pools like druid/c3p0, it is necessary to optimized the part on obtaining ConnectionInfo of the database that have not yet implemented monitoring to avoid NPE.
None of these databases have plugins to track SQL statements now, and adding these URLParsers can make connection pools report pool metrics of these databases successfully.
Search before asking
Description
current DB types in URLParser :
I want to add URL parsing types:
Use case
When the database connection pool connecting to
Derby/Sybase/SQLite/DB2/OceanBase
, JDBC URL can be parsed and the monitoring meters can be reported.Related issues
No response
Are you willing to submit a pull request to implement this on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: