[00:55:25] <jinxer-wm>	 FIRING: SystemdUnitFailed: wmf_auto_restart_prometheus-mysqld-exporter.service on db1280:9100 - https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state - https://grafana.wikimedia.org/d/g-AaZRFWk/systemd-status - https://alerts.wikimedia.org/?q=alertname%3DSystemdUnitFailed
[04:58:55] <jinxer-wm>	 FIRING: SystemdUnitFailed: wmf_auto_restart_prometheus-mysqld-exporter.service on db1280:9100 - https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state - https://grafana.wikimedia.org/d/g-AaZRFWk/systemd-status - https://alerts.wikimedia.org/?q=alertname%3DSystemdUnitFailed
[07:48:55] <jinxer-wm>	 RESOLVED: SystemdUnitFailed: wmf_auto_restart_prometheus-mysqld-exporter.service on db1280:9100 - https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state - https://grafana.wikimedia.org/d/g-AaZRFWk/systemd-status - https://alerts.wikimedia.org/?q=alertname%3DSystemdUnitFailed
[10:04:42] <jynus>	 I did my update on the phab tasks, so it is neatly organized there
[10:04:58] <jynus>	 feel free to ask any questions if there are any
[10:48:59] <jynus>	 I didn't know Percona was the closest thing to an Orchestator maintainer: https://github.com/percona/orchestrator
[10:49:38] <jynus>	 since last year
[10:50:05] <cezmunsta>	 ProxySQL took stewardship of it this year, around April time iirc
[10:50:43] <jynus>	 ah, that wasn't on the repo
[10:51:27] <jynus>	 it isn't under their organization though
[10:51:32] <cezmunsta>	 https://proxysql.com/blog/announcing-proxysql-takes-over-orchestrator
[10:52:24] <cezmunsta>	 I would check the bugs though...
[10:52:45] <jynus>	 👀
[10:56:50] <cezmunsta>	 The reason that Percona created the fork was that it was part of the distribution for MySQL and that also it was used within Managed Services. Development was limited to issues affected their customers, rather than what ProxySQL have done. At least last time that I checked anyway
[10:57:13] <jynus>	 Yeah, that matches the explanation
[11:18:05] <jynus>	 have a nice weekend