-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose config metrics #93
Expose config metrics #93
Conversation
Config metrics are not currently not exposed by the exporter. These metrics are used in some existing dashboards. Config metrics being exposed: - max_client_conn: pgbouncer_config_max_client_conn - max_user_connections: pgbouncer_config_max_user_connections Signed-off-by: kenneth-duffel <93927344+kenneth-duffel@users.noreply.github.com> Signed-off-by: kenneth-duffel <kenneth@duffel.com>
Following a PR comment, this updates the metric name to a preferred name. Signed-off-by: kenneth-duffel <kenneth@duffel.com>
451819f
to
f579834
Compare
Thanks you |
Dear @SuperQ and @kenneth-duffel I have been using {"caller":"collector.go:474","err":"error retrieving columns list from SHOW CONFIG: <nil>\n","level":"error","msg":"error getting SHOW CONFIG","ts":"2023-01-26T18:51:11.176Z"} I have PgBouncer 1.17.0 where I have more than 3 colums:
It should be at least 3, or do I miss something? pgbouncer_exporter/collector.go Lines 189 to 192 in 07052df
UPDATE: I found it, so the code expects these 3 columns in this order but I have pgbouncer_exporter/collector.go Lines 199 to 201 in 07052df
Based on the documentation (https://www.pgbouncer.org/usage.html) there are 4 columns:
|
Config metrics are not currently not exposed
by the exporter. These metrics are used in some
existing dashboards.
Config metrics being exposed:
Signed-off-by: kenneth-duffel 93927344+kenneth-duffel@users.noreply.github.com