You are browsing a read-only backup copy of Wikitech. The live site can be found at


From Wikitech-static
< WMDE‎ | Wikidata
Revision as of 21:24, 8 September 2021 by imported>Ladsgroup (→‎Grafana)
Jump to navigation Jump to search


Wikidata contact information for Alertmanager is set in

The status of alerts can be seen at

Internally in WMDE there is a wikidata-monitoring mailing list you can subscribe to.

All alerts coming from grafana with tag of team: "wikidata-team" and receiver of Alertmanager will end up contacting the wikidata-monitoring internal mailing list. (See Alertmanager for more information on how to setup alerts that would contact the team).


Alertmanager handle wikidata alerts dashboard on Grafana.

The dashboard can be found here:

Maxlag: Above 10 for 1 hour

In the past this has been caused by:

  • dispatch lag being high, due to waiting for replication, due to a db server being overloaded, due to a long running query that was not correctly killed

Dispatch Script starts

A script is regularly run by Cron to inform other wikis about changes in Wikidata. If that script is not run for longer time than that indicates a problem. This script runs on as well, so there is an alert for that too in order to maybe spot a problem there before it reaches production with the train a day later.

The previous incident: T258062: Wikidata Change Dispatching Broken

See also WMDE/Wikidata/Dispatching and Wikibase: Change propagation

Edits: Wikidata edit rate

The edit rate on Wikidata can be a good indicator that something somewhere is wrong, although it will not always indicate exactly what that is.

You can view the edits dashboard at

If MAXLAG is high, that might be a reason for low edit rate.

You may want to investigate what is going on with the API (as all edits go via the API)*

API: Max p95 execute time for write modules

Investigate the wb api @*

In the past this has been caused by:

  • s8 db being overloaded, often for a fixable reason
  • Memcached being overloaded, in the past indicating UBNs

Termbox Request Errors

This kind of error occurs when Wikibase is unable to reach the Termbox Service, i.e. the HTTP request itself fails and is unlikely to have reached its destination. This error does *not* get triggered by erroneous responses, so it means there is a problem on the MediaWiki/Wikibase side or network issues.

Oozie Job

Sometimes these jobs will fail for random reasons.

They will be restarted, so no need to worry on a first failure.

If things continue to fail, contact WMF analytics to investigate on IRC in #wikimedia-analytics.