Affects Version/s: 2.3.0, 2.4.0
Fix Version/s: 2.7.0
docker container with 2.3.0 pmm-server:2
alertmanager in another docker container
Sprint:Platform Sprint 12, Platform Sprint 16, Platform Sprint 17, Platform Sprint 18
- Install PMM2 2.3.0
- Configure Alertmanager (run was-staging-start job with --setup-alertmanager option)
- Open PMM settings page
- Add alert manager url and rule
- Apply changes
- Check PMM_Server/prometheus/rule page. Added rule should be displayed
- Open Pmm Settings page
- Change Alertmanager rule and submit the form
- Check again PMM_Server/prometheus/rule page
Expected result: the new rule is displayed
Given result: The old rule is displayed
Expected results: Prometheus alerting rules changes shouldn't need docker restart
See Smart Checklist.
following yout blog about alertmanager I tried it.
Starting with the mentioned Postgres down rule I got it working, but any changes to the alertmanager rules in the GUI did not fire on the testet values.
In the comments of the blog article I found "try to look http:///prometheus"
This worked with the docker container on https://<pmmserver>:8443/prometheus and there only the Postgres Down Rule was mentioned. After docker stop/start the new rules also are mentioned.
Please make prometheus reloading the alertmanager rules after the "Aplly Alertmanager Settings" button in pmm-settings is pressed and the rules are valid.
Thanks again for the PMM itself. Very helpful tool.