Hi Nuria, Thank you so much for your help on this. Please let me know if there is any way I can help out or if there is anything you need from our end.
Joel Joel Sahleen, Software Engineer Language Engineering Wikimedia Foundation [email protected] On Nov 13, 2014, at 9:42 AM, Nuria Ruiz <[email protected]> wrote: > Hello, > > Taking last statement back, asked Yuvi and beta does have a varnish instance > so the flow of EL events "should" be the same one that production. > > Now I looked on deployment-eventlogging02, which is the EL machine for labs > and the last events I see there are from Aug 22. > > So no events have come in as of late, which could point to an issue on the > setup. I will look into it some more. > > Thanks, > > Nuria > > On Wed, Nov 12, 2014 at 10:40 AM, Nuria Ruiz <[email protected]> wrote: > To keep archives happy: Beta setup post events to > http://bits.beta.wmflabs.org/event.gif that, while it does not look to be > varnish, has some kind of listener that post those events to beta event > logging database. > > On Wed, Nov 12, 2014 at 9:37 AM, Joel Sahleen <[email protected]> wrote: > Niklas, > > Can you answer this question from Nuria? > > jsahleen: does beta have its own varnish instance? where are you posting your > events in beta? can you send teh url? > > Also would it be possible to document the steps you used when testing EL on > beta so that others can reproduce them? > > Thanks, > > Joel > > Joel Sahleen, Software Engineer > Language Engineering > Wikimedia Foundation > [email protected] > > > > > On Nov 12, 2014, at 4:28 AM, Joel Sahleen <[email protected]> wrote: > >> (Moving this discussion to analytics@ and localization-team@ based on >> Nuria’s suggestion below.) >> >> Hi Leila, >> >> The output I posted in the message is the only output I am seeing. I do not >> see the URL-encoded section or the validation section. I think there may be >> something wrong with my testing setup. >> >> Niklas Laxstöm has checked what is happening with our event logging in beta >> and he confirmed that we are sending events and the events are valid. The >> issue seems to be that we are logging events to the beta event logging db >> while what we checked earlier was the production event logging db. >> >> Can you (or anyone who is available) check the event logging db in beta to >> see if the table has been created and has data? The schema name again is >> ContentTranslation. If you don’t find anything, let us know and we will do >> some more investigation. >> >> If there is data in the beta db the next step would be to follow with Dan’s >> instructions to get a dashboard set up on limn1. I believe that most of >> Dan’s instructions need to be handled by someone on the analytics team, but >> let me know if there is anything I can help with. >> >> Thanks again for your help! >> >> Joel >> >> Joel Sahleen, Software Engineer >> Language Engineering >> Wikimedia Foundation >> [email protected] >> >> >> >> >> On Nov 11, 2014, at 11:47 PM, Leila Zia <[email protected]> wrote: >> >>> Hi Joel, >>> >>> When you log events, the output will be the URL-encoded JSON sent by the >>> browser, the event record (similar to what you pasted in your email), and >>> whether the event validates against the schema. For the sample output you >>> pasted earlier, or another sample output, can you let us know if validation >>> section shows Valid? >>> >>> Leila >>> >>> On Mon, Nov 10, 2014 at 3:24 PM, Nuria Ruiz <[email protected]> wrote: >>> Joel, >>> >>> For questions like these going forward you can contact analytics@ as you >>> will be getting amore prompt response. Both Dan and Leila are OOTO the >>> next couple of days. >>> >>> >There are configuration options for the dev server that need to be added. >>> >Do similar options need to be added when not using the dev server? >>> No, there is no need. >>> >>> You would need sample rates to determine at which sampling rate you are >>> logging if you are not logging all events, that is. >>> >>> Thanks, >>> >>> Nuria >>> >>> On Mon, Nov 10, 2014 at 2:39 PM, Dan Andreescu <[email protected]> >>> wrote: >>> Adding Nuria as she can probably help >>> >>> On Monday, November 10, 2014, Joel Sahleen <[email protected]> wrote: >>> Hi Leila, >>> >>> I have tested our EventLogging code and it seems to be working fine with >>> the event logging dev server. I can see the events coming through and they >>> are valid. Here is some sample output: >>> >>> {"wiki": "wiki", "uuid": "e9dde14cf18552269ae81a7897f45d0c", "webHost": >>> "localhost", "timestamp": 1415651367, "clientValidated": true, "recvFrom": >>> "1.0.0.127.in-addr.arpa", "seqId": 2, "clientIp": >>> "80f7683f3565e3d365740a1c8d1771ba95caaaaa", "schema": "ContentTranslation", >>> "event": {"action": "create-translated-page", "targetLanguage": "ca", >>> "token": "Tester", "version": 1, "contentLanguage": "es"}, "revision": >>> 7146627} >>> >>> Are there additional configuration options we need to add to get EL working >>> aside from just requiring the main extension file. There are configuration >>> options for the dev server that need to be added. Do similar options need >>> to be added when not using the dev server? >>> >>> Any help on this would be much appreciated. >>> >>> Thanks, >>> >>> Joel >>> >>> On Nov 7, 2014, at 3:52 PM, Joel Sahleen <[email protected]> wrote: >>> >>>> No problem, Dan. Enjoy your vacation! >>>> >>>> I will read through the document at the link you sent. I still need to fix >>>> our event logging code so it may be a couple days before we are ready >>>> anyway. If I have any questions I will contact Leila or Nuria. >>>> >>>> Thanks, >>>> >>>> Joel >>>> >>>> Joel Sahleen, Software Engineer >>>> Language Engineering >>>> Wikimedia Foundation >>>> [email protected] >>>> >>>> >>>> >>>> >>>> On Nov 7, 2014, at 3:10 PM, Dan Andreescu <[email protected]> wrote: >>>> >>>>> Joel, re: visualization, >>>>> >>>>> I'm going on vacation tomorrow and will be back on November 19th. If >>>>> that's not too late, I can set up a limn instance then. If it's too >>>>> late, that's ok, I wrote up the steps needed. Someone with access to the >>>>> limn1.eqiad.wmflabs instance can perform them: >>>>> https://wikitech.wikimedia.org/wiki/Analytics/Dashboards >>>>> >>>>> If you have the data or are generating the data in some other way, then >>>>> you don't need half of that setup, you just need the part that sets up >>>>> the limn dashboard which is only an hour or so of work. Sorry I'm >>>>> running out the door and can't take care of that for you. >>>>> >>>>> Dan >>>>> >>>>> On Fri, Nov 7, 2014 at 7:37 AM, Joel Sahleen <[email protected]> >>>>> wrote: >>>>> Thank you for the information, Pau. Very helpful. As you say, this does >>>>> not change our current plans or hold us up in any way. I was just wasn’t >>>>> clear about the relationship between the "high priorities" and "other >>>>> metrics” sections. Knowing these came from different people at different >>>>> times clarifies things a lot. >>>>> Joel >>>>> >>>>> On Nov 7, 2014, at 3:44 AM, Pau Giner <[email protected]> wrote: >>>>> >>>>>> @Pau, @Amir There is a section called High priorities for product >>>>>> management on the Content translation analytics page. Did these >>>>>> priorities come from outside the team or does this just represent our >>>>>> own internal view of the high priorities? >>>>>> >>>>>> Here is the story of that page as I'm aware of it: >>>>>> >>>>>> In September 2013, I was in a meeting with the analytics team in SF >>>>>> presenting an initial proposal for metrics. On that meeting, Dario >>>>>> recommended to create hierarchy of metrics based on the project goals. I >>>>>> created such image and a description for those metrics (the image is on >>>>>> top of our analytics page and the metrics are described in what it now >>>>>> the "Other metrics for created articles" section. >>>>>> >>>>>> In a meeting between Amir and Howie, they captured which should be the >>>>>> most important metrics from the product perspective in the "High >>>>>> priorities for product management". If I recalled correctly, as an >>>>>> outcome of later meetings between Howie and Amir, Howie was happy >>>>>> focusing on articles published as a single (initial?) metric for >>>>>> success. Amir can provide more details since I was not on those meetings. >>>>>> >>>>>> In short: The analytics page has pieces contributed by different people >>>>>> during the last year, and although there are many ideas to organise and >>>>>> detail, measuring the number of published articles seems to be the solid >>>>>> candidate to get started with, learn from the value we get from it and >>>>>> polish the rest of our goal-to-signal process for detecting better >>>>>> metrics. >>>>>> >>>>>> >>>>>> Pau >>>>>> >>>>>> On Fri, Nov 7, 2014 at 1:57 AM, Joel Sahleen <[email protected]> >>>>>> wrote: >>>>>> Hi All, >>>>>> >>>>>> I have been reviewing our requirements for Content translation analytics >>>>>> and I have a few questions/requests. I am sending them to the language >>>>>> team list and Leila and Dan in the hopes of getting some more clarity. I >>>>>> will add the same content to the Trello card. >>>>>> >>>>>> In the weekly team meeting earlier today we agreed that the first metric >>>>>> we want to collect data for is the number of articles created in each >>>>>> language over time. This is something has Amir has already set up our >>>>>> current Event Logging to track. Now that Kartik has enabled EL in beta, >>>>>> that part should be done. Since we are only barely turning it on, there >>>>>> will be very little data until people create more articles using CX. >>>>>> However, we should be set up to collect any new data that comes in. >>>>>> >>>>>> @Leila, can you verify that the db table now exists for the >>>>>> ContentTranslation schema? If it doesn’t, can you point us to right >>>>>> people we need to work with to troubleshoot the issue? Also you >>>>>> mentioned in our meeting that personal data may soon be purged after 90 >>>>>> days as part of a new privacy policy. Could you explain that a bit more >>>>>> or point us to more information? If this is the case, it may affect some >>>>>> of the metrics we would like to collect in the future. >>>>>> >>>>>> @Dan, what do we need to do next in order to set up a very simple >>>>>> visualization that would show the number of articles created per week by >>>>>> language. Pau has an image of what he would like on the Trello card. You >>>>>> mentioned something about being able to host a dashboard for us on one >>>>>> of the Limn servers you already have set up. >>>>>> >>>>>> @Santhosh, I believe you said earlier you have a script you use to >>>>>> export the data for the ULS analytics. If so can you share that please >>>>>> in case we need a similar script for CX so I don’t have to write a new >>>>>> script from scratch? >>>>>> >>>>>> @Pau, @Amir There is a section called High priorities for product >>>>>> management on the Content translation analytics page. Did these >>>>>> priorities come from outside the team or does this just represent our >>>>>> own internal view of the high priorities? If the latter, have these >>>>>> priorities been reviewed by anyone outside the team? I think we are safe >>>>>> to proceed with our current plan, but it would be good to have product >>>>>> sign off on things more generally. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Joel >>>>>> >>>>>> Joel Sahleen, Software Engineer >>>>>> Language Engineering >>>>>> Wikimedia Foundation >>>>>> [email protected] >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Localisation-team mailing list >>>>>> [email protected] >>>>>> https://lists.wikimedia.org/mailman/listinfo/localisation-team >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Pau Giner >>>>>> Interaction Designer >>>>>> Wikimedia Foundation >>>>>> _______________________________________________ >>>>>> Localisation-team mailing list >>>>>> [email protected] >>>>>> https://lists.wikimedia.org/mailman/listinfo/localisation-team >>>>> >>>>> >>>> >>> >>> >>> >> > > > _______________________________________________ > Analytics mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/analytics > > > > _______________________________________________ > Localisation-team mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/localisation-team
_______________________________________________ Analytics mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/analytics
