rock-n-code/deep-linking-sample
rock-n-code/deep-linking-sample
1
0
Fork 0
Code Pull Requests Releases 2 Wiki Activity
deep-linking-sample/Apps/Wikipedia/docs/event_logging.md
Javier Cicchelli 9bcdaa697b [Setup] Basic project structure (#1) 
This PR contains all the work related to setting up this project as required to implement the [Assignment](https://repo.rock-n-code.com/rock-n-code/deep-linking-assignment/wiki/Assignment) on top, as intended.

To summarise this work:
- [x] created a new **Xcode** project;
- [x] cloned the `Wikipedia` app and inserted it into the **Xcode** project;
- [x] created the `Locations` app and also, its `Libraries` package;
- [x] created the `Shared` package to share dependencies between the apps;
- [x] added a `Makefile` file and implemented some **environment** and **help** commands.

Co-authored-by: Javier Cicchelli <javier@rock-n-code.com>
Reviewed-on: rock-n-code/deep-linking-assignment#1
2023-04-08 18:37:13 +00:00

1.7 KiB
Raw Permalink Blame History

Event logging

Note: Testing event logging requires labs access to deployment-eventlog05.eqiad.wmflabs

To test event logging:

  • ensure event logging is enabled via Gear icon > Send usage reports

  • select Staging scheme in Xcode, then in Configuration's current property, change the staging options to return Configuration.staging(options: [.deploymentLabsForEventLogging]).

  • get the app install id:

    • run app in the simulator
    • pause
    • paste po [[NSUserDefaults standardUserDefaults] wmf_appInstallId]; in the Xcode console and copy the resulting string

  • ssh to labs: ssh deployment-eventlog05.eqiad.wmflabs

  • tail the following files (tail keeps stream open and prints last few lines of a file any time it changes) with the app install id and the id of the schema being tested (from MPopov):

    • /srv/log/eventlogging/all-events.log
      • only has events which have been validated against the appropriate schemas
    • /srv/log/eventlogging/client-side-events.log
      • has all incoming events (as raw, encoded URI query strings) regardless of their validity
    • /var/log/eventlogging/eventlogging-processor@client-side-00.log
    • /var/log/eventlogging/eventlogging-processor@client-side-01.log
      • if there are any issues with the incoming events or their validation, there will be detailed messages in the two eventlogging-processor@-client-side-XX logs

    Example:

    • tail -f /srv/log/eventlogging/all-events.log | grep "<app install id>" | grep "<schema id>"