[00:50:25] <jinxer-wm>	 FIRING: SystemdUnitFailed: curator_actions_cluster_wide.service on logging-sd2001: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
[03:05:25] <jinxer-wm>	 RESOLVED: SystemdUnitFailed: curator_actions_cluster_wide.service on logging-sd2001: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
[18:22:34] <topranks>	 Folks is there any way to see why CI is unhappy with a patch in the alerts repo?  
[18:22:43] <topranks>	 I have one it's not happy about:  https://gerrit.wikimedia.org/r/c/operations/alerts/+/1229163
[18:23:14] <topranks>	 I tested locally with "promtool test rules" and it seemed happy 
[18:23:33] <topranks>	 the output in jenkins doesn't give me much info about what is wrong, but hopefully I'm just missing where that is 
[18:31:39] <cdanis>	 topranks: jenkins ui 'feature', you need to click through to the child job or whatever heh https://integration.wikimedia.org/ci/job/alerts-pipeline-test/3188/console
[18:32:38] <topranks>	 cdanis; ah thanks!  
[18:32:52] <topranks>	 you know I've hit that before and knew what to do and somehow today it escapes me 
[18:32:53] <topranks>	 cheers :) 
[18:33:08] <cdanis>	 np :D