Hi Nuria,
Thank you for proofreading this. I clearly misunderstood some of the files.
I think it would be great if you could add some documentation to that wiki
page about the various files in the /var/log/eventlogging folder.
It would be nice to sort them in order messages flow (unvalidated ->
validated, ...).
Also I think it would be useful to restructure the page based on types of
consumers of the page: one section on top for event logging users, and
another one for admins below. In other words I think the Database and "Raw
stream of events" sections could be moved up, and then everything
afterwards is admin stuff.
Here are a few more questions in the mean-time:
* Is my assumption correct that we devs can no longer access production EL
data?
* If so, do we client side devs even need access to stat1002/1003? (Or what
would it be useful for?) I'm asking because this is one of the onboarding
steps we have for new developers, and next week we'll have another dev
joining our team.
Thanks,
Bernd
On Mon, Apr 20, 2015 at 5:50 PM, Nuria Ruiz <nuria(a)wikimedia.org> wrote:
(cc-ing analytics list)
Heads up, that the way we test Event Logging has
changed.
Details can be found here:
https://wikitech.wikimedia.org/wiki/EventLogging/Testing/BetaLabs
Correct, analytics team will take care of maintaining these docs.
ssh eventlogging02.eqiad.wmflabs
cd /var/log/eventlogging
tail -f client-side-events.log
This will give you the WHOLE stream of client side
events, correct, valid
and invalid.
For unvalidated events check out the file
all-events.log instead.
This log holds VALID events both client and server side.
2. Modify event logging code in client code
In Android app uncomment the following line in EventLoggingEvent
// private static final String EVENTLOG_URL = "
http://bits.beta.wmflabs.org/event.gif"quot;;
Correct
3. Run your code, and see the output from step 1.
Correct
Thanks for testing before sending your code to prod!
Nuria
On Mon, Apr 20, 2015 at 2:03 PM, Bernd Sitzmann <bernd(a)wikimedia.org>
wrote:
Hi Nuria,
I'm about to send this off to the mobile-tech list. But before I do that,
is this info correct?
Thanks,
Bernd
---
Heads up, that the way we test Event Logging has changed. Details can be
found here:
https://wikitech.wikimedia.org/wiki/EventLogging/Testing/BetaLabs
1.
ssh eventlogging02.eqiad.wmflabs
cd /var/log/eventlogging
tail -f client-side-events.log
For unvalidated events check out the file all-events.log instead.
If you need access check out
https://wikitech.wikimedia.org/wiki/EventLogging/Testing/BetaLabs#Give_peop…
.
2. Modify event logging code in client code
In Android app uncomment the following line in EventLoggingEvent
// private static final String EVENTLOG_URL = "
http://bits.beta.wmflabs.org/event.gif"quot;;
Please don't commit that change to keep the production value as is.
3. Run your code, and see the output from step 1.
As an aside:
Confused about beta and labs, like I was? Check out
https://wikitech.wikimedia.org/wiki/Labs_labs_labs. For some reason when
I joined it was called beta labs and that stuck with me, and for a lot of
others, like the creator of the page
https://wikitech.wikimedia.org/wiki/EventLogging/Testing/BetaLabs.
Cheers,
Bernd
