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
PGBouncer has been updated and now exposes more metrics than before - the exporter no longer supports the full list of metrics and the following error can be seen in the logs of the exporter:
could not get store result: could not get stats: unexpected column: total_server_assignment_count
The support has been added in upstream pg_exporter, supporting pgbouncer version 1.24 and up.
The pgbouncer base image was updated to 1.24 in the airflow-pgbouncer-2025.01.10-1.24.0 docker image, however the exporter has not been updated to support it.
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Apache Airflow version
2.10.5
If "Other Airflow 2 version" selected, which one?
No response
What happened?
PGBouncer has been updated and now exposes more metrics than before - the exporter no longer supports the full list of metrics and the following error can be seen in the logs of the exporter:
The support has been added in upstream pg_exporter, supporting pgbouncer version 1.24 and up.
The pgbouncer base image was updated to 1.24 in the airflow-pgbouncer-2025.01.10-1.24.0 docker image, however the exporter has not been updated to support it.
The defaults for the helm chart are currently;
Which are not compatible.
What you think should happen instead?
The exporter should be compatible with the version of pgbouncer deployed.
How to reproduce
Deploy the latest helm chart enabling pgbouncer, the logs for the
metrics-exporter
container in the pgbouncer pod will indicate the errorOperating System
Ubuntu 22.04
Versions of Apache Airflow Providers
No response
Deployment
Official Apache Airflow Helm Chart
Deployment details
pgbouncer enabled
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: