[10:02:43] <icinga-wm>	 PROBLEM - High lag on wdqs1003 is CRITICAL: 5411 ge 3600 https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook%23Update_lag https://grafana.wikimedia.org/dashboard/db/wikidata-query-service?orgId=1&panelId=8&fullscreen
[10:03:15] <icinga-wm>	 RECOVERY - Free Blazegraph allocators wdqs-blazegraph on wdqs1006 is OK: All metrics within thresholds. https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook https://grafana.wikimedia.org/dashboard/db/wikidata-query-service?orgId=1&panelId=32&fullscreen
[10:03:56] <Lucas_WMDE>	 hm, looks like wdqs1003 didn’t report any lag data at all for 1½ hours
[10:04:14] <Lucas_WMDE>	 same for other metrics
[10:05:26] <Lucas_WMDE>	 wait, no, the one I see in Grafana is wdqs1006, not 3
[10:50:03] <Lucas_WMDE>	 well, it looks like the host is recovering, at least
[11:30:11] <icinga-wm>	 RECOVERY - High lag on wdqs1003 is OK: (C)3600 ge (W)1200 ge 1068 https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook%23Update_lag https://grafana.wikimedia.org/dashboard/db/wikidata-query-service?orgId=1&panelId=8&fullscreen
[13:45:46] <Reedy>	 wikibase repo tests are sloooooooowwwwwwwww