Prometheus PostgreSQL Exporter for a Tower PostgreSQL Jet
Deploy a Dockerized PostgreSQL Exporter that discovers a running PostgreSQL Jet and exposes its metrics for Prometheus.
Summary
- Category
- Jet Templates
- Tags
- Monitoring
- Authors
- Cetmix OÜ
- License
- AGPL-3
- Version
- 1.0.0
- Call sign
- jet_template_postgres_exporter
- Website
- cetmix.com/contact
This snippet imports a PostgresExporter Jet Template using quay.io/prometheuscommunity/postgres-exporter:v0.20.1. It allows one exporter per server and requires a running postgres_docker Jet on that server. The YAML includes the PostgreSQL 17 dependency template, with optional pgBackRest backups, and the Docker, Fail2ban and Tower Core dependencies.
Deploy and scrape
- Import the YAML and install the exporter template on the PostgreSQL host. Set
postgres_passwordin Tower Keys and Secrets and ensurepostgres_usermatches the PostgreSQL login. When enabling S3 backups for the bundled PostgreSQL Jet, configure its repository settings and theaws_key_idandaws_access_keysecrets. - Set
postgres_exporter_portand create an exporter Jet targeting Running. Prepare resolves the running PostgreSQL container name and stores it inpostgres_exporter_host. Build renders a credential-bearing environment file under the Jet root and uses it to configure the container's connection to thepostgresdatabase on port5432. The database connection usessslmode=disableon the shared Docker network. - Allow the Prometheus server to reach
postgres_exporter_port(typically TCP9187), checking the effective filtering of Docker-published ports. The exporter publishes this port directly without Traefik. - Run Refresh targets on Prometheus. Check the
postgresjob andpg_up. Grafana uses the Tower server name as the instance.
Operate
Use Rebuild after changing the database connection or exporter image. Restart reuses the container's existing environment. If pg_up is zero, verify the PostgreSQL Jet, resolved hostname, credentials and Docker network. The template also provides Stop, Remove and Destroy actions for the exporter.
This package is distributed under the GNU Affero General Public License v3.0 (AGPL-3) or later.
These Terms and Conditions (“Terms”) govern your access to and use of YAML configuration files (“Packages”, “YAML Snippets”, or “Snippets”) made available via the Cetmix Tower platform, operated by Cetmix OÜ, Ranna 6, Haademeeste, Voiste, 86501, Estonia (“Cetmix”, “we”, “our”, or “us”).
By downloading, installing, or otherwise using any YAML Snippets from the Cetmix Tower platform, you agree to be bound by these Terms.
1. Use of Packages
1.1. The YAML Snippets are provided either by Cetmix or third-party authors (“Authors”).
1.2. You are solely responsible for verifying the functionality, safety, and suitability of any YAML Snippet before using it in a production environment.
1.3. You may use the Snippets only in accordance with their respective licenses, which may be open-source or commercial.
2. Author Responsibility
2.1. Authors are solely responsible for the content, accuracy, functionality, and compliance of the YAML Snippets they publish.
2.2. Cetmix does not review or verify the correctness, security, or compliance of third-party Snippets.
2.3. If you are an Author, you represent and warrant that your submitted YAML Snippet:
- Does not infringe on any third-party rights;
- Complies with applicable laws and regulations;
- Does not contain harmful, malicious, or misleading code or behavior.
3. Limitation of Liability
3.1. Cetmix provides access to the YAML Snippets “as is” and “as available,” without warranties of any kind, either express or implied.
3.2. Cetmix expressly disclaims all liability for any damages resulting from:
- Use or inability to use a YAML Snippet;
- Errors or omissions in the Snippets;
- Actions taken in reliance on any YAML Snippet;
- Misuse, misconfiguration, or system failure caused by a Snippet.
3.3. In no event shall Cetmix OÜ be liable for any indirect, incidental, special, punitive, or consequential damages, including but not limited to loss of data, profits, or service availability.
4. Security and Compliance
4.1. Cetmix does not guarantee that any Snippet is secure or free from vulnerabilities. You must review and test all Snippets before deploying them in sensitive or production environments.
4.2. Compliance with security, privacy, and regulatory requirements is your responsibility when using any Snippet.
5. Intellectual Property
5.1. Ownership of each YAML Snippet remains with its respective Author.
5.2. You must respect all license terms specified for each Snippet. Unauthorized reproduction, distribution, or sublicensing may result in legal consequences.
6. Modifications and Termination
6.1. Cetmix may modify or remove any YAML Snippet at any time without notice.
6.2. These Terms may also be updated periodically. Continued use of the platform constitutes acceptance of the revised Terms.
7. Governing Law and Jurisdiction
These Terms shall be governed by the laws of the Republic of Estonia. Any disputes arising under or in connection with these Terms shall be subject to the exclusive jurisdiction of the courts of Estonia.
8. Contact
For questions or concerns regarding these Terms or specific YAML Snippets, please contact us