Page MenuHomePhabricator

Add meta data from the run to the page drill down pages
Closed, ResolvedPublic

Description

In our drill down pages (https://grafana.wikimedia.org/d/IvAfnmLMk/page-drilldown) we show the video and the screenshot from the latest runs. But we also have meta data from that run (browser version, exact URL tested and when running tests on Android we have phone and Android version). We should include that data too on the dashboard to make it easier to understand what we actually test.

Event Timeline

It will look something like this:

Screenshot 2022-03-24 at 10.44.14.png (1,294×306 px, 53 KB)

Change 774001 had a related patch set uploaded (by Phedenskog; author: Phedenskog):

[performance/synthetic-monitoring-tests@master] Update version that have more meta data to show in Grafana.

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

Change 774001 merged by jenkins-bot:

[performance/synthetic-monitoring-tests@master] Update version that have more meta data to show in Grafana.

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

Change 774380 had a related patch set uploaded (by Phedenskog; author: Phedenskog):

[operations/puppet@production] grafana: provision JSON datasource

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

Change 778469 had a related patch set uploaded (by Phedenskog; author: Phedenskog):

[operations/puppet@production] grafana: double-proxy for performance JSON meta data

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

Change 778469 merged by Cwhite:

[operations/puppet@production] grafana: double-proxy for performance JSON meta data

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

Proxy config rolled out, but curl'ing the endpoint raises a 500:

AH01144: No protocol handler was valid for the URL / (scheme 'https'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.

Contrast with:

$ curl -i --proxy http://webproxy.codfw.wmnet:8080 https://synthetic-tests-result-wikimedia.s3.amazonaws.com/`
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>132...E4MX</RequestId><HostId>JOK3...2Ig=</HostId></Error>

mod_ssl is not enabled on these hosts. Perhaps it is needed to proxy to https endpoints?

Enabling it may be tricky. Envoy holds port 443 and apache2 attempts to bind it if mod_ssl is enabled.

Change 784294 had a related patch set uploaded (by Phedenskog; author: Phedenskog):

[operations/puppet@production] grafana: Fix performance team JSON proxy.

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

@colewhite thank you I missed that. Changed so we proxy http to http.

Change 784294 merged by Cwhite:

[operations/puppet@production] grafana: Fix performance team JSON proxy.

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

Mentioned in SAL (#wikimedia-operations) [2022-04-25T19:09:09Z] <cwhite> install grafana-plugins 0.5 and restart grafana on grafana1002 T304583

Change 774380 merged by Cwhite:

[operations/puppet@production] grafana: provision JSON datasource

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

Changes are now applied to production grafana.