Intake request has been filed for the superset dashboard creation: T412137: Personal Dashboard Instrumentation Superset Dashboard

Change #1223193 had a related patch set uploaded (by Kgraessle; author: Kgraessle):

[mediawiki/extensions/PersonalDashboard@master] Instrument the Page Visit health metric for PersonalDashboard extension

https://gerrit.wikimedia.org/r/1223193

Change #1223201 had a related patch set uploaded (by Kgraessle; author: Kgraessle):

[mediawiki/extensions/WikimediaEvents@master] Instrument the Page Visit health metric for PersonalDashboard extension

https://gerrit.wikimedia.org/r/1223201

This isn't ready to be merged yet, but can be tested and reviewed on the engineering side.

kgraessle opened https://gitlab.wikimedia.org/repos/modtools/vitest-plugin/-/merge_requests/11

Add mock hook implementation to mw mock

dhardy merged https://gitlab.wikimedia.org/repos/modtools/vitest-plugin/-/merge_requests/11

Add mock hook implementation to mw mock

Ok, I rolled up both T407275: Instrument Recent Activity Module and T407280: Instrument Content Policy module and Impact Module into the same two patches as this ticket since the changes were not large.

• https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikimediaEvents/+/1223201
• https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PersonalDashboard/+/1223193

Note I have stalled out all of the instrumentation tickets until we're able to merge the following fix in https://phabricator.wikimedia.org/T414174. Though we should be able to test locally and do engineering review in the meantime.
I also need to fix one issue with a unit test and the extension registry, but will talk about this in engineering weekly.

Note you can run the following command to get around the config fetching issue locally:

docker compose exec mediawiki maintenance/run.php ./extensions/TestKitchen/maintenance/UpdateConfigs.php

I also need to fix one issue with a unit test and the extension registry, but will talk about this in engineering weekly.

Noting that this issue is fixed and we are now waiting on the patch on T414174: Automatically fetch instrument configs in local dev environment to be merged.

Change #1223201 merged by jenkins-bot:

[mediawiki/extensions/WikimediaEvents@master] Instrument health metrics for PersonalDashboard extension

https://gerrit.wikimedia.org/r/1223201

Change #1223193 merged by jenkins-bot:

[mediawiki/extensions/PersonalDashboard@master] Instrument health metrics for PersonalDashboard extension

https://gerrit.wikimedia.org/r/1223193

verified dashboard link tracking on stathost notebook:

import wmfdata as wmf
query='select count(*) from event.product_metrics_web_base where element_friendly_name = "Personal Dashboard menu link";'
result = wmf.spark.run(query)
result

We haven't figured out how to query page views by instrument name, so we can't validate that part through a stat host ATM.

Query for page views:

wmf.spark.run("""
SELECT * FROM event.product_metrics_web_base WHERE instrument_name='personal-dashboard-health-metrics' AND action ='pageview' AND month=2 AND day=19 AND year=2026 LIMIT 3;
"""

@Kgraessle - I'm currently seeing many users where we log impressions and clicks (action IN ('click', 'impression')) but not a pageview (action = 'pageview'). See query below.

Do you know why these instances would occur?

SELECT
      performer.name AS user_name,
      SUM(IF(action = 'pageview', 1, 0)) AS pv_count,
      SUM(IF(action = 'impression', 1, 0)) AS imp_count,
      SUM(IF(action = 'click', 1, 0)) AS click_count
  FROM event.product_metrics_web_base 
  WHERE 
      instrument_name = 'personal-dashboard-health-metrics'
      AND YEAR = 2026
      AND MONTh = 02
      AND DAY >= 19
  GROUP BY 1

In T407278#11640771, @MNeisler wrote:

@Kgraessle - I'm currently seeing many users where we log impressions and clicks (action IN ('click', 'impression')) but not a pageview (action = 'pageview'). See query below.

Do you know why these instances would occur?

SELECT
      performer.name AS user_name,
      SUM(IF(action = 'pageview', 1, 0)) AS pv_count,
      SUM(IF(action = 'impression', 1, 0)) AS imp_count,
      SUM(IF(action = 'click', 1, 0)) AS click_count
  FROM event.product_metrics_web_base 
  WHERE 
      instrument_name = 'personal-dashboard-health-metrics'
      AND YEAR = 2026
      AND MONTh = 02
      AND DAY >= 19
  GROUP BY 1

Hi! @MNeisler
It looks like that query is capturing all impressions and because we have an impression on each page with the navigation menu link you'll get a lot.
I modified your query slightly to filter out events with that element_friendly_name of "Personal Dashboard menu link" and the numbers look about right.

SELECT
      performer.name AS user_name,
      SUM(IF(action = 'pageview', 1, 0)) AS pv_count,
      SUM(IF(action = 'impression', 1, 0)) AS imp_count,
      SUM(IF(action = 'click', 1, 0)) AS click_count
  FROM event.product_metrics_web_base 
  WHERE 
      instrument_name = 'personal-dashboard-health-metrics'
      AND YEAR = 2026
      AND MONTh = 02
      AND DAY >= 19
      AND (
          element_friendly_name IS NULL
          OR element_friendly_name NOT LIKE '%Personal Dashboard menu link%'
        )
  GROUP BY 1

Let me know if you have any other questions.

Got it. The pageview numbers look correct with that additional filter. Thanks for clarifying!