Alertmanager with Docker and Tower Webhook Routing
Run Prometheus Alertmanager in Docker and forward every alert to a Cetmix Tower webhook with bearer-token authentication.
Summary
- Category
- Jet Templates
- Tags
- Monitoring
- Authors
- Cetmix OÜ
- License
- AGPL-3
- Version
- 1.0.0
- Call sign
- jet_template_alertmanager
- Website
- cetmix.com/contact
This snippet imports an Alertmanager Jet Template using prom/alertmanager:v0.28.1. It allows one instance per server, keeps its data and configuration under the Jet root and runs as nobody (65534) on the shared Docker network. Port 9093 is not published, so Prometheus reaches Alertmanager by its container name. Alertmanager groups alerts by tower_server and sends them all to a single Tower webhook, repeating them every alertmanager_repeat_interval (10m by default). The Docker, Fail2ban and Tower Core dependency templates are included.
Configure and launch
- Import the YAML and install the template on the monitoring server. Docker must be running on it.
- Set the value of the Alertmanager Webhook Token secret. Use the same value in the bearer authenticator of the Tower webhook that receives the alerts (see the separate Alertmanager webhook snippet).
- Set
alertmanager_webhook_urlto<tower_url>/cetmix_tower_webhooks/<endpoint>. The default is a placeholder, so replace it with your own Tower URL. Keepalertmanager_repeat_intervalbelow the stale-after time of the metrics it carries. - Create a Jet targeting Running. Prepare creates the data and config directories and locks the Jet against deletion. Build pushes
alertmanager.ymland the token file, fixes ownership, pulls the image and creates the container. Start brings it online. - In
prometheus.ymladdalerting.alertmanagerswith the target<alertmanager_jet_reference>:9093and yourrule_files, then reload Prometheus.
Operate and troubleshoot
After changing the webhook URL, the repeat interval or the token, run Reload config. It re-pushes both files, restores ownership and sends SIGHUP, so the container is not recreated. Rebuild recreates the container from the current image tag and keeps the data directory. The Jet logs show the container output and the result of the Alertmanager health probe. If no alerts reach Tower, check the Jet logs, the webhook URL and that the token matches the authenticator. Destroy removes the container, image, files, DNS record, root directory and volumes of the Jet.
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