Reset
Report Status
Date
Duration
Name
Playbook name (or path) Host facts
1 09 Jun 2025 16:22:58 +0100 00:00:27.61 hn19.j.layershift.co.uk ...ansible/kuly/raid_m/upload_raid.yaml
1 09 Jun 2025 15:04:34 +0100 00:00:24.38 hn19.j.layershift.co.uk ...usr/local/bin/raid_monit.pl
1 09 Jun 2025 15:03:33 +0100 00:00:24.30 hn19.j.layershift.co.uk Ad-Hoc: shell: ls -la /usr/local/bin/raid_monit*
1 09 Jun 2025 15:02:41 +0100 00:00:57.31 hn19.j.layershift.co.uk ...ansible/kuly/raid_m/upload_raid.yaml
09 Jun 2025 15:01:19 +0100 00:00:04.48 hn19.j.layershift.co.uk Ad-Hoc: shell: lsattr /usr/local/bin/raid_monit*
09 Jun 2025 15:01:07 +0100 00:00:06.84 hn19.j.layershift.co.uk Ad-Hoc: shell: ls -la /usr/local/bin/raid_monit*
09 Jun 2025 15:00:49 +0100 00:00:12.59 hn19.j.layershift.co.uk ...usr/local/bin/raid_monit.pl
1 09 Jun 2025 14:49:33 +0100 00:00:22.95 hn19.j.layershift.co.uk Ad-Hoc: shell: ls -la /usr/local/bin/raid_*
1 09 Jun 2025 14:48:27 +0100 00:00:25.11 hn19.j.layershift.co.uk Ad-Hoc: ping
1 17 Mar 2025 16:02:07 +0000 00:00:13.94 hn19.j.layershift.co.uk Ad-Hoc: shell: service netdata restart
1 17 Mar 2025 16:01:31 +0000 00:00:04.41 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 17 Mar 2025 16:01:14 +0000 00:00:14.59 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 17 Mar 2025 16:00:43 +0000 00:00:03.72 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 17 Mar 2025 16:00:32 +0000 00:00:03.73 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 17 Mar 2025 16:00:21 +0000 00:00:04.69 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 17 Mar 2025 16:00:09 +0000 00:00:04.38 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 17 Mar 2025 15:58:41 +0000 00:00:04.04 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 15 Nov 2024 10:56:55 +0000 00:00:13.32 hn19.j.layershift.co.uk ...conf.d/health_alarm_notify.conf| grep -v NO
1 15 Nov 2024 10:53:47 +0000 00:00:14.38 hn19.j.layershift.co.uk ...conf.d/health_alarm_notify.conf| grep -v NO
1 15 Nov 2024 10:31:33 +0000 00:00:09.91 hn19.j.layershift.co.uk ...conf.d/health_alarm_notify.conf| grep -v NO
1 15 Nov 2024 10:29:48 +0000 00:00:09.70 hn19.j.layershift.co.uk ...conf.d/health_alarm_notify.conf| grep -v NO
1 15 Nov 2024 10:22:44 +0000 00:00:08.26 hn19.j.layershift.co.uk ...conf.d/health_alarm_notify.conf| grep -v NO
1 1 15 Nov 2024 10:21:31 +0000 00:00:09.71 hn19.j.layershift.co.uk ...conf.d/health_alarm_notify.conf| grep -v NO
15 Nov 2024 10:21:07 +0000 00:00:04.16 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 1 15 Nov 2024 10:20:12 +0000 00:01:50.69 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
15 Nov 2024 10:18:08 +0000 00:00:07.22 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 1 11 Jun 2024 10:32:16 +0100 00:00:10.26 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 1 11 Jun 2024 10:31:54 +0100 00:00:10.00 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 1 11 Jun 2024 10:24:57 +0100 00:00:09.94 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 1 11 Jun 2024 10:16:44 +0100 00:00:10.05 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 1 11 Jun 2024 10:16:31 +0100 00:00:12.67 hn19.j.layershift.co.uk ...health_alarm_notify.conf; service netdata restart
1 1 11 Jun 2024 10:14:57 +0100 00:00:10.06 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 1 11 Jun 2024 10:11:12 +0100 00:00:10.52 hn19.j.layershift.co.uk ...lib/netdata/conf.d/health_alarm_notify.conf
1 11 Jun 2024 10:10:20 +0100 00:00:05.08 hn19.j.layershift.co.uk Ad-Hoc: ping