---
name: "prometheus-pgbouncer-exporter"
section: "1"
platform: "linux"
package: "prometheus-pgbouncer-exporter"
version: "1:0.10.2-2"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/prometheus-pgbouncer-exporter"
---

# prometheus-pgbouncer-exporter(1)

Prometheus exporter for PgBouncer

## NAME

prometheus-pgbouncer-exporter - Prometheus exporter for PgBouncer

## SYNOPSIS

- **prometheus-pgbouncer-exporter \[\<flags\>\]**

  ## DESCRIPTION

## OPTIONS

- **-h, --help**

  Show context-sensitive help (also try --help-long and --help-man).

- **--log.level=info**

  Only log messages with the given severity or above. One of: \[debug, info, warn, error\]

- **--log.format=logfmt**

  Output format of log messages. One of: \[logfmt, json\]

- **--pgBouncer.connectionString**

  Connection string for accessing pgBouncer.

- **--web.telemetry-path**

  Path under which to expose metrics.

- **--pgBouncer.pid-file**

  Path to PgBouncer pid file.

  	If provided, the standard process metrics get exported for the PgBouncer\
   	process, prefixed with 'pgbouncer\_process\_...'. The pgbouncer\_process exporter\
   	needs to have read access to files owned by the PgBouncer process. Depends on\
   	the availability of /proc.

  	https://prometheus.io/docs/instrumenting/writing\_clientlibs/#process-metrics.

- **--web.systemd-socket**

  Use systemd socket activation listeners instead of port listeners (Linux only).

- **--web.listen-address=:9127**

  Addresses on which to expose metrics and web interface. Repeatable for multiple addresses. Examples: \`:9100\` or \`\[::1\]:9100\` for http, \`vsock://:9100\` for vsock

- **--web.config.file**

  Path to configuration file that can enable TLS or authentication. See: https://github.com/prometheus/exporter-toolkit/blob/master/docs/web-configuration.md

- **--version**

  Show application version.