[11:41:04] <icinga-wm>	 RECOVERY - Check unit status of analytics-dumps-fetch-mediacounts on clouddumps1002 is OK: OK: Status of the systemd unit analytics-dumps-fetch-mediacounts https://wikitech.wikimedia.org/wiki/Analytics/Systems/Managing_systemd_timers
[13:31:06] <icinga-wm>	 RECOVERY - Check unit status of analytics-dumps-fetch-unique_devices on clouddumps1002 is OK: OK: Status of the systemd unit analytics-dumps-fetch-unique_devices https://wikitech.wikimedia.org/wiki/Analytics/Systems/Managing_systemd_timers
[13:59:00] <wikibugs>	 (03CR) 10Aklapper: "@Ottomata, @Nuria: Should this be abandoned per T174796?" [analytics/refinery/source] (nav-vectors) - 10https://gerrit.wikimedia.org/r/383761 (https://phabricator.wikimedia.org/T174796) (owner: 10Shilad Sen)
[15:47:20] <wikibugs>	 10Data-Engineering: Generate data to count langswitches for every article - https://phabricator.wikimedia.org/T310975 (10Kanzat)
[17:27:08] <wikibugs>	 10Analytics, 10Documentation: Document our level of support of pyspark-based jobs - https://phabricator.wikimedia.org/T274775 (10Aklapper)
[17:46:15] <wikibugs>	 10Data-Engineering, 10Project-Admins: Archive Analytics tag - https://phabricator.wikimedia.org/T298671 (10Aklapper) @odimitrijevic: Could you please answer? Not finishing this creates confusion as people continue to tag #Analytics on tasks. Thanks.
[17:47:07] <wikibugs>	 10Data-Engineering, 10Project-Admins: Archive Analytics tag - https://phabricator.wikimedia.org/T298671 (10Aklapper) Also CC'ing @JArguello-WMF
[17:48:13] <wikibugs>	 10Data-Engineering: Documentathon - https://phabricator.wikimedia.org/T311413 (10Aklapper) Is there any timeframe related to this? In theory searching for tasks with both (#Documentation && (#Data-Engineering OR #Analytics)) should list quick ideas, which then could be (de)prioritized instead?
[19:29:39] <wikibugs>	 10Analytics-Wikistats, 10Data-Engineering-Kanban, 10Data Engineering Planning (Sprint 01): Use dedicated Phabricator bug report / feature request forms - https://phabricator.wikimedia.org/T308610 (10Aklapper) 05Open→03Resolved a:05Milimetric→03Aklapper Boldly closing as `resolved` as my patch has bee...
[22:14:10] <icinga-wm>	 PROBLEM - MegaRAID on an-worker1082 is CRITICAL: CRITICAL: 13 LD(s) must have write cache policy WriteBack, currently using: WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough https://wikitech.wikimedia.org/wiki/MegaCli%23Monitoring
[23:00:07] <icinga-wm>	 RECOVERY - MegaRAID on an-worker1082 is OK: OK: optimal, 13 logical, 14 physical, WriteBack policy https://wikitech.wikimedia.org/wiki/MegaCli%23Monitoring
[23:34:36] <icinga-wm>	 PROBLEM - MegaRAID on an-worker1082 is CRITICAL: CRITICAL: 13 LD(s) must have write cache policy WriteBack, currently using: WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough, WriteThrough https://wikitech.wikimedia.org/wiki/MegaCli%23Monitoring
[23:46:06] <icinga-wm>	 RECOVERY - MegaRAID on an-worker1082 is OK: OK: optimal, 13 logical, 14 physical, WriteBack policy https://wikitech.wikimedia.org/wiki/MegaCli%23Monitoring