Marking this as completed as the first version is functional. Additional tasks can be filed for additions/improvements.

Seems like it coincides, the jobs were scheduled to run on 5th of every month.

I re-ran manually, everything is back up again.

Okay, I don't know what happened, I re-ran the scripts manually again, they ran fine. Not sure if this needs to be further investigated, or probably a one-off connection issue at the time of the monthly update.

@bd808 Any thoughts on this? As the errors seem similar to T189386 & T183644

Triaging this as high as it affecting at least two public facing dashboards.

The data is now updated and the charts are working.

@santhosh The Airflow pipeline is fixed, I will re-run the Toolforge update scripts.

I have updated the dashboard to include rowiki.

Thanks Miriam. I will update this task with more concrete support items we might need for Q2.

The analysis and the outputs have been shared with Halley.

cc @cchen @OSefu-WMF

Yes, this is not relevant. Reportupdater is no longer (I think). But all the pipelines are based on Airflow

@GGoncalves-WMF I have been able to work with the scripts Marcel and Jennifer developed for processes the logs - super helpful! A quick question, the logs at /srv/log/webrequest/archive/dumps.wikimedia.org/ and then processed. I am curious about what process publishes logs to that location - is it solely from webrequests or some other source?

I don't think it is possible with any of the available contextual attributes. I have to check with Exp Platform on this one.

Hi @Miriam! I can definitely say until end of Q2. At the moment, I don't know yet what needs might evolve for Q3 and beyond. If needed, I make a new request or update this one - will that work?

cc @OSefu-WMF

@MartinRulsch sorry, I completely missed your question, sorry for about that. In future, feel free to ping again or send an email if something hasn't been replied for long.

@GGoncalves-WMF thank you!

Hi all, as this analysis will inform a decision within the WE5 scope of work, so I can take this up (confirmed with @HCoplin-WMF on Slack).

Posting the A/A test and A/B test experiment flow here as well, and when a pagevisit event should be logged.

Tagging @cchen for QA.

For the current Synthetic A/A test, are we ONLY interested in tracking the page visit event, and not the entry points to visit MinT wiki readers (which would be handled in a later A/B test)

Do we interested if user leave the page and possible because of page loading time?
if yes then we need to log the "duration" as well when page unload.
Note: Currently, there is no "unload" log event

@hueitan thanks for pointing that. Please use fy25-26-we-3-1-5-mint-readers

The dashboard is functional at: https://superset.wmcloud.org/superset/dashboard/unified-cx-metrics/

no schema changes are required, just updating the ID is fine. 1.4.2 includes the experiment related fields, which will be used when the experiment is live.

I had a Slack conversation ongoing with @BTullis about this.

@cchen and I had a conversation with @SBisson last week, and based on that conversation, I think it is better to split the baseline measurements based on the change being done and measured appropriately. A single measure, for example just article quality may not work as there are multiple changes. The changes being done within the CX workflow are: (@SBisson: please correct if I am wrong)

I am unable to verify editor_close, editor_close_warn and publish_failure from the browser console. It would be helpful if someone else can QA these events.

QA results

When user click on the "confirm step", we log the duration (from page load to user confirm) time together with the click, let me know what's the context key for it

@cchen will take this up as she will be supporting WE2.

per Product Analytics allocation changes

@ngkountas

The above QA tested the "Invite after translation" entrypoint, but the task is about the "Invite to translate a section recently edited in another language" entrypoint (recent edit entrypoint).

Confirming that the dashboard translation start events are being logged for this entry point with event source as followup_after_publishing

Can you check once more? I see this still happening at the same level: https://logstash.wikimedia.org/goto/bcd0e6e008b59f4d4bfdf117e55ad8fc