Page MenuHomePhabricator

Metrics Platform Integration: Verify that we can query for the data points that were captured by Metrics Platform on Superset or Turnilo
Closed, ResolvedPublic

Description

Once events are being sent in production, we need to verify that we can query for the data points that were captured by Metrics Platform on Superset or Turnilo so that the collection loop is complete.

Acceptance Criteria

  • Events sent from Community Updates collected by Metrics Platform are visible on Superset or Turnilo

Details

Other Assignee
mforns

Event Timeline

@Sgs @Cyndymediawiksim Can T374464 be a child of this?

Sure. This task needs to wait for the community updates module to be enabled in at least one production wiki, so the relevant table is accessible from Superset.

Cyndymediawiksim lowered the priority of this task from High to Low.
Cyndymediawiksim moved this task from Backlog to FY2024-25 Q1 Sprint 6 on the Growth-Team board.

Both dashboards are present in supereset. Pinging @nettrom_WMF for checking if the dashboards have the needed info. Two notes

  • changing filters often produce erorrs, e.g. changing Time to Last month or Last day instead of default Last quarter on dashboard/552 results in Unexpected error. However, it's outside the scope of this task.
  • (super minor) the title SDS 2 Sprinthackular 2024 - Community Updates per-defines the specific part of any title on a dashboard. Since it's rather long, the specific part of the title (e.g. CTR per update) got hidden:
    Screen Shot 2024-10-03 at 11.53.54 AM.png (784×2 px, 122 KB)

Both dashboards are present in supereset. Pinging @nettrom_WMF for checking if the dashboards have the needed info. Two notes

  • changing filters often produce erorrs, e.g. changing Time to Last month or Last day instead of default Last quarter on dashboard/552 results in Unexpected error. However, it's outside the scope of this task.

Thanks @Etonkovidova for noticing this, the change in date filter causing errors seems to be a client-side timeout issue. The timeout settings in Superset might be too short for these queries. See superset FAQ docs for more information on this.

  • (super minor) the title SDS 2 Sprinthackular 2024 - Community Updates per-defines the specific part of any title on a dashboard. Since it's rather long, the specific part of the title (e.g. CTR per update) got hidden:
    Screen Shot 2024-10-03 at 11.53.54 AM.png (784×2 px, 122 KB)

We can make a quick change to abbreviate the dashboard title prefix. Can you suggest a preferred short version?

Both dashboards are present in supereset. Pinging @nettrom_WMF for checking if the dashboards have the needed info. Two notes

  • changing filters often produce erorrs, e.g. changing Time to Last month or Last day instead of default Last quarter on dashboard/552 results in Unexpected error. However, it's outside the scope of this task.

Thanks, @Cyndymediawiksim - yes, it's outside the scope. Btw, it's a rather common issue for superset. I've seen on other teams' dashboards too.

Thanks @Etonkovidova for noticing this, the change in date filter causing errors seems to be a client-side timeout issue. The timeout settings in Superset might be too short for these queries. See superset FAQ docs for more information on this.

  • (super minor) the title SDS 2 Sprinthackular 2024 - Community Updates per-defines the specific part of any title on a dashboard. Since it's rather long, the specific part of the title (e.g. CTR per update) got hidden:
    Screen Shot 2024-10-03 at 11.53.54 AM.png (784×2 px, 122 KB)

We can make a quick change to abbreviate the dashboard title prefix. Can you suggest a preferred short version?

Hmm... we may ask @KStoller-WMF and @nettrom_WMF for the titles naming.

Hmm... we may ask @KStoller-WMF and @nettrom_WMF for the titles naming.

I think shortening to Community Updates makes sense (remove SDS 2 Sprinthackular 2024 -).

Can we also remove (testwiki data) from the title, or will this dashboard really only ever be usable for testwiki?