Last modified: 2014-05-30 20:21:59 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 T67872, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 65872 - MobileWikiOperatorCode Schema
MobileWikiOperatorCode Schema
Status: RESOLVED WORKSFORME
Product: Analytics
Classification: Unclassified
EventLogging (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-28 19:17 UTC by dr0ptp4kt
Modified: 2014-05-30 20:21 UTC (History)
7 users (show)

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


Attachments

Description dr0ptp4kt 2014-05-28 19:17:16 UTC
Ori asked me to create this bug for tracking.

The backing store in the EventLogging database corresponding to https://meta.wikimedia.org/w/index.php?title=Sche
ma:MobileWikiOperatorCode&oldid=8678522, which is the product of a Move, may not be taking events.

With https://gerrit.wikimedia.org/r/#/c/135599/1/includes/MccMncLogging.php deployed, it seems that the legacy MobileOperatorCode_8365469 wasn't getting events nor was MobileWikiAppOperatorCode_8678522 created (thus not taking events).
Comment 1 dr0ptp4kt 2014-05-28 19:24:21 UTC
To be clear, it's not that the entire database isn't taking events - I doubt that - but rather that the specific tables may not be taking events from what we could see when querying this morning.
Comment 2 nuria 2014-05-29 11:11:43 UTC
If your event is not being recorded the two likely scenarios are:

1. it does not validate 

2. it is not being published 

As far as I  can see there is no mention of MobileWikiAppOperatorCode in the all-events.log in vanadium, thus I believe your event is not being published.
Comment 3 dr0ptp4kt 2014-05-29 14:58:48 UTC
How about now? I just made an additional 200 API requests (random article API request) to en.m.wikipedia.org bearing the header needed by the API, so at 2% sampling one would hope something would show.

Or are you referring to something more fundamental in the event publication?
Comment 4 nuria 2014-05-29 16:12:41 UTC
>How about now? I just made an additional 200 API requests (random article API >request) to en.m.wikipedia.org bearing the header needed by the API, so at 2% >sampling one would hope something would show.
Have you tested locally the publication of events? Please do so as we do not want to "test" even publication in production.
 
If you do not know how to test locally event publication please take a look at doc (link below) and send us an e-mail if you need help. If you have a mediawiki vagrant install it should be easy to see whether events are being published.

https://www.mediawiki.org/wiki/Extension:EventLogging/Guide
Comment 5 dr0ptp4kt 2014-05-29 18:00:20 UTC
Yes, fortunately, it's working locally. For example, tailing on the log file, and issuing a bunch of http://localhost:8080/w/api.php?action=query&list=random&rnnamespace=0&rnlimit=2 (at 2% sampling, or turning up the sampling, more frequently) -

vagrant@mediawiki-vagrant:/vagrant/logs$ tail -f eventlogging.log

{"event":{"ip":"10.0.2.2","mccMnc":"000-00"},"schema":"MobileWikiAppOperatorCode","revision":8678522,"clientValidated":false,"wiki":"wiki","recvFrom":"mediawiki-vagrant.dev","timestamp":1401385688,"webHost":"localhost:8080"}

Any thoughts on next steps on production? Do you happen to see any MobileWikiAppOperatorCode entries in prod now? I have an access request in flight to get in for querying on my own eventually, but was wondering if you had seen anything now (at 2% sampling, would expect about 7 records by now).

Thanks!
Comment 6 Ori Livneh 2014-05-30 20:21:59 UTC
mysql:root@localhost [log]> select count(*) from MobileWikiAppOperatorCode_8678522;
+----------+
| count(*) |
+----------+
|       11 |
+----------+
1 row in set (0.00 sec)

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


Navigation
Links