-
Notifications
You must be signed in to change notification settings - Fork 232
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
problem getting PgBouncer metrics because of "SET lock_timeout TO '100ms';" #507
Comments
here is a part of my tf config [for db in var.pw2_monitored_dbs : {
unique_name = db.unique_name
dbtype = "pgbouncer"
host = db.host
port = db.port
user = db.username
password = db.password
dbname = db.dbname
sslmode = "require"
stmt_timeout = 15
is_superuser = false
is_enabled = true
group = "default"
sslrootcert = ""
sslcert = ""
sslkey = ""
custom_metrics = {
pgbouncer_stats = 60
}
} if db.dbtype == "pgbouncer"] i think |
from aiven pgbouncer, with v1.9.0
|
I'm getting similar errors to Martin.
@pmpetit It seems like the user you log in with is not added as an admin in pgbouncer.ini |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have some issues collecting PgBouncer metrics.
It seems pgwatch2 is issuing these two statements to get PgBouncer version, but the first one fails:
SET lock_timeout TO '100ms';show version
If I login to pgbouncer at port 6432 as pgbouncer to pgbouncer DB and manually issue SET lock_timeout statement it also fails:
I'm using PostgreSQL 14.5, PgBouncer 1.17.0 and pgwatch2 1.9.0.
The command to start pgwatch2 is:
/usr/bin/pgwatch2-daemon -c /etc/pgwatch2/config/instances.yaml -m /etc/pgwatch2/metrics --datastore=prometheus
The error log from pgwatch2 when I hit the prometheus endpoint:
Content of
/etc/pgwatch2/config/instances.yaml
:I'm not entirely sure if my config is OK.
Can you please help? Thank you.
The text was updated successfully, but these errors were encountered: