Last modified: 2014-07-31 02:16:54 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T70357, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68357 - Add basic monitoring for GlobalRename
Add basic monitoring for GlobalRename
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Kunal Mehta (Legoktm)
:
Depends on: 68356
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-22 00:21 UTC by Kunal Mehta (Legoktm)
Modified: 2014-07-31 02:16 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Kunal Mehta (Legoktm) 2014-07-22 00:21:31 UTC
Basically we should be able to notice if a global rename takes longer than say 10 minutes (maybe an hour for a large edit count) without waiting for a steward or the user to notice.

This can be something simple on labs probably.
Comment 1 Marius Hoch 2014-07-22 08:50:48 UTC
While I totally agree that we need something like this, I still think that 10 minutes or even an hour aren't enough time... during high load or if a global account has a lot of local ones it's totally ok for a rename to take a few hours (maybe 3?).

We shouldn't make people go crazy with false (to early) alerts.
Comment 2 Kunal Mehta (Legoktm) 2014-07-31 02:16:54 UTC
I made how long to wait configurable, so we can adjust as needed.

Setup a tool on toollabs ("gblrenamemon"), which will email me (and anyone else who wants to be added to the list!) if a rename takes over 3 hours to complete. The cron runs every 20 minutes.

Source code is in labs/tools/gblrenamemon.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links