Page MenuHomePhabricator

Ensure operational visibility in ChronologyProtector
Open, Needs TriagePublic

Description

I think I need more metrics (e.g. percentage of executions of chronology protector vs. successful executions) because either this didn't work, its measurements are not accurate for what we really want to measure, or it worked and displayed worse lag issues than we thought.

This might be instrumented already, in which case it's (only) a matter of setting up a dashboard and/or documenting it somewhere.

Event Timeline

Krinkle created this task.Oct 11 2019, 3:40 AM
Restricted Application added a project: Core Platform Team. · View Herald TranscriptOct 11 2019, 3:40 AM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Change 542458 had a related patch set uploaded (by Aaron Schulz; owner: Aaron Schulz):
[mediawiki/core@master] rdbms: add ILBFactory::setDefaultReplicationWaitTimeout() method

https://gerrit.wikimedia.org/r/542458

Change 542466 had a related patch set uploaded (by Aaron Schulz; owner: Aaron Schulz):
[mediawiki/core@master] rdbms: inject replLogger into Database and consolidate duplicate logging

https://gerrit.wikimedia.org/r/542466

Change 542458 merged by jenkins-bot:
[mediawiki/core@master] rdbms: add ILBFactory::setDefaultReplicationWaitTimeout() method

https://gerrit.wikimedia.org/r/542458

Change 542466 merged by jenkins-bot:
[mediawiki/core@master] rdbms: inject replLogger into Database and consolidate duplicated logging

https://gerrit.wikimedia.org/r/542466