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
Is your feature request related to a problem? Please describe.
Currently, when adding new metrics with the sqlquery receiver, the receiver sets up a new connection for each query.
We currently have more than 40 of these metrics, which means Open Telemetry opens more than 40 database connections.
Describe the solution you'd like
It would be better if the PostgreSQL Connection pool feature would be available for this receiver too, so that the amount of database connections can be reduced.
Describe alternatives you've considered
Updating the maximum number of connections so that more connections are allowed, but this means the database needs more resources to keep all these connections open.
Additional context
No response
The text was updated successfully, but these errors were encountered:
I took a quick look, sounds like a good enhancement to me.
it looks like this functionality is provided by golang's standard SQL package (example usage here), and can be implemented with all supported SQL drivers. This would require adding new configuration options and plumbing them down to here:
Component(s)
receiver/sqlquery
Is your feature request related to a problem? Please describe.
Currently, when adding new metrics with the sqlquery receiver, the receiver sets up a new connection for each query.
We currently have more than 40 of these metrics, which means Open Telemetry opens more than 40 database connections.
Describe the solution you'd like
It would be better if the PostgreSQL Connection pool feature would be available for this receiver too, so that the amount of database connections can be reduced.
Describe alternatives you've considered
Updating the maximum number of connections so that more connections are allowed, but this means the database needs more resources to keep all these connections open.
Additional context
No response
The text was updated successfully, but these errors were encountered: