- create the wikitech page as WMDE/Wikidata/Runbooks/Change dispatching/Alert
- clearly identify the potential alert that might be triggered, so that this page can also be found when searching for snippets from alert emails
- link it to WMDE/Wikidata/Dispatching
- move information from https://wikitech.wikimedia.org/wiki/WMDE/Wikidata/Alerts#Change_Dispatching there
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T307073 Job queue backlog time increases for the `wikibase-InjectRCRecords` and `refreshLinks` jobs | |||
| Resolved | ItamarWMDE | T327641 [TECH][WIKIDATA] Create an incident playbook/flow chart for what to do when Wikidata ChangeDispatching is lagging | |||
| Resolved | Michael | T349173 Create runbook page on Wikitech and link it to Wikidata Dispatch documentation there |
Event Timeline
Comment Actions
A first version now exists at https://wikitech.wikimedia.org/wiki/WMDE/Wikidata/Runbooks/Change_dispatching/Alert. Its main purpose is to elaborate on the alerts and link to the documentation. Further subtasks to the parent task will mention how to triage and fix some of the alerts.
In the context of this, the following related but separate stories were created:
Comment Actions
Looks good to me so far; I also created an index at WMDE/Wikidata/Runbooks (but didn’t link it at WMDE/Wikidata yet, I think that can wait until the end of the parent task).
Comment Actions
link it to WMDE/Wikidata/Dispatching
What direction of link does this AC require? From the runbook to the dispatching docs, and/or the other way around? (AFAICT the dispatching docs don’t link to the runbook yet.)
Comment Actions
(Otherwise ready for tech verification, I think, unless we think as a subtask it should be directly closed and only the parent task goes to tech verification later?)
Comment Actions
From the runbook to the docs, I think. As a replacement to trying again to explain how it works in the runbook.
Yes, my understanding is that we usually only request verification for completed stories, not for subtasks.