Grafana Dashboards with Prometheus and Traefik

Deploy Grafana with a preconfigured Prometheus datasource and HTTPS access through Traefik.

Summary

Category: Jet Templates
Tags: Monitoring
Authors: Cetmix OÜ
License: AGPL-3
Version: 1.0.0
Call sign: jet_template_grafana
Website: cetmix.com/contact

This snippet imports a Grafana Jet Template using grafana/grafana:13.2.0 and includes the Prometheus, Traefik, Docker, Fail2ban and Tower Core templates. Grafana runs once per server alongside its running Prometheus and Traefik dependencies. It stores dashboards and other Grafana data under the Jet root and provisions a default Prometheus datasource over the shared Docker network. Traefik serves Grafana over HTTPS using its Jet hostname and routes to container port 3000.

Configure and launch

Import the YAML and install the Grafana template on the monitoring server. Set grafana_admin_password in Tower Keys and Secrets and choose grafana_admin_user (default admin).
Set web_domain and ensure the Grafana hostname resolves to Traefik. Set Traefik's instance_certbot_email and make ports 80 and 443 reachable for HTTP-01 and HTTPS. For automatic Cloudflare DNS registration, set cloudflare_token and cloudflare_zone_id. If using an ACME DNS challenge, populate the selected provider's credentials in Tower as well (cloudflare_token, digitalocean_api_token, hetzner_api_token, or aws_dns_key_id and aws_dns_access_key).
Configure the bundled Prometheus Jet's prometheus_retention and exporter port variables (node_exporter_port, cadvisor_port and postgres_exporter_port). Set prometheus_sd_postgres_legacy to a JSON array or [] for an empty list. Create the Grafana Jet targeting Running, and open its HTTPS URL.

View metrics and manage Grafana

Add dashboards that use the provisioned datasource. For new hosts, deploy the relevant exporter Jets, allow Prometheus to reach their ports and run Refresh targets on Prometheus. Use jobs node, cadvisor and postgres and select the Tower server name as the instance. If a dashboard is empty, verify scrape status in Prometheus and datasource connectivity in Grafana.

Build renders the administrator credentials into the mounted grafana.ini file. Start, Restart and a running Rebuild apply the credentials from that file to the existing Grafana instance. Rebuild replaces the container while retaining its data directory. Destroy removes the deployment and its local Grafana data.

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