Dustin C. Hatch
6f9cd7e4af
It turns out, having the exporter connect to the _template1_ database is not a great idea. PostgreSQL does not allow creating a new database if the template database is currently being accessed by any clients. Since _template1_ is the default choice, the `createdb` command will probably fail. It doesn't specifically matter which database the exporter connects to, since it reads most (all?) of its data from the PostgreSQL catalog, which isn't database-specific.
20 lines
549 B
Django/Jinja
20 lines
549 B
Django/Jinja
[Unit]
|
|
Description=PostgreSQL Exporter for Prometheus
|
|
Wants=network-online.target
|
|
After=network-online.target
|
|
After=postgresql.service
|
|
|
|
[Container]
|
|
Image=quay.io/prometheuscommunity/postgres-exporter:v0.15.0
|
|
Environment=DATA_SOURCE_URI='postgres-exporter@:5432/postgres?host=/run/postgresql'
|
|
Mount=type=bind,source=/run/postgresql,target=/run/postgresql
|
|
# container_t cannot access the PostgreSQL socket postgresql_var_run_t
|
|
SecurityLabelDisable=true
|
|
User=221
|
|
Group=221
|
|
DropCapability=all
|
|
PublishPort=9187:9187
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|