action #170338
Updated by mkittler 1 day ago
## Observation
https://monitor.qa.suse.de/d/WebuiDb/webui-summary?orgId=1&from=2024-11-25T14:15:24.661Z&to=2024-11-25T14:58:43.878Z&var-host_disks=$__all&refresh=15m
## Acceptance criteria
* **AC1:** There is current monitoring data from OSD itself on monitor.qa.suse.de
* **AC2:** There is also monitoring data after reboots of monitor+OSD
## Acceptance tests
* **AT1-1:** https://monitor.qa.suse.de/d/WebuiDb/webui-summary?orgId=1&from=now-7d&to=now&var-host_disks=$__all&refresh=15m&viewPanel=panel-78 shows current data
* **AT2-1:** Same as AT1-1 but reboot monitor in before
* **AT2-2:** Same as AT1-1 but reboot OSD in before
## Suggestions
* Handle IPv4+IPv6 double routing problems after setting up wireguard tunnels disrupting also our monitoring
* Understand what approach to take for routing with VPN in place and consider both source and target hosts for communication
* Might need changes to multiple hosts
* Make changes persistent in salt
* Ensure reboot consistency
## Rollback actions
* Remove alert from https://monitor.qa.suse.de/alerting/silences called `rule_uid=~host_up_alert.*`
Back