What about replag? The bot would puke every time that replication stops. On Mar 10, 2009, at 8:02 PM [Mar 10, 2009 ], Robert Rohde wrote:
> On Tue, Mar 10, 2009 at 4:43 PM, K. Peachey > <p858sn...@yahoo.com.au> wrote: >> On Wed, Mar 11, 2009 at 9:21 AM, Robert Rohde <raro...@gmail.com> >> wrote: >>> Out of curiousity, when a technical problem shuts down all >>> editing on >>> a major wiki (as this did) are there any automated alerts? Is it >>> likely to be noticed and addressed even if no one rushes to IRC? >>> >>> I guess I am curious what is the normal delay between problem onset >>> and problem recognition? >>> >>> -Robert Rohde >> I believe with this issue (Full MySQL table) that there is no easy >> way >> to automate the test..... >> maybe you could automatically query it every so often but even then >> that might not return reliable results. > > One could query count(*) from revisions (or some similar artifice, > such as looking at the recent changes feed) and trigger an alert if it > stops increasing. > > Such things are probably totally unnecessary on enwiki, because there > is no shortage of people to complain, but I could image it might be > useful to have such an alert for smaller, non-English speaking wikis. > > -Robert Rohde > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
