Sudden spike in SQL connection metrics on the grafana dashboard

[aryanmehrotra]

Describe the bug
Sql connection count reaches 143 but actually the total number of db connections from all my pods to the database never exceeded 50 - have verified from cloudSQL, most probably wrong metrics is being pushed or something related to the query

using the gofr default for - DB_MAX_IDLE_CONNECTION, DB_MAX_OPEN_CONNECTION

**Environments (please complete the following information): **

• OS: Linux
• gofr version - v1.46.1
• go version -1.25

[Umang01-hash]

@aryanmehrotra The discrepancy between our metrics (143 connections) and CloudSQL (50 connections) is due to how Go's database/sql package counts connections versus how database servers report them.

• stats.OpenConnections counts ALL connections managed by Go's connection pool, including both active and idle connections.
• Database monitoring tools like CloudSQL typically only count active connections to the server.

Moreover, If you want metrics that match what CloudSQL shows, use: app_sql_inUse_connections as they represents active connections that are currently executing queries, which is what database monitoring tools typically count.

metrics.SetGauge("app_sql_inUse_connections", float64(stats.InUse))

[aryanmehrotra]

then we should be updating this in the gofr_application_monitoring dashboard - https://grafana.com/grafana/dashboards/19905-gofr-application-services-monitoring-2/