Secure config page load times
Looking at https://dashboards.gitlab.net/d/product-secure/product-performance-secure?orgId=1
I feel we are perhaps not recording the following pages we may wish to keep an eye on
@matt_wilson i feel like we should add the Vulnerability report? https://gitlab.com/gitlab-org/secure/general/-/security/vulnerability_report
@derekferguson i feel we should add the on-demand scan pages? https://gitlab.com/gitlab-org/secure/general/-/on_demand_scans
@sam.white i assume protect has a different grafana board?
I think we should add the sec config page https://gitlab.com/gitlab-org/secure/general/-/security/configuration
Who owns audit events? https://gitlab.com/gitlab-org/secure/general/-/audit_events
we need to: https://about.gitlab.com/handbook/product/product-processes/#page-load-performance-metrics
Adding additional pages to performance testing The Grafana dashboards are managed using grafonnet, making it easy to add additional pages and charts.
Testing a new set of pages requires just 2 steps:
Add the desired URL's to the sitespeed unauthenticated or authenticated testing list. Add a new line with the URL, then a space, and an alias of the form [Group][Feature][Detail]. The alias needs to be one word, an example MR is here. Note the authenticated user account does not have any special permissions, it is simply logged in. Open the relevant stage's grafonnet dashboard file. Find the section corresponding to the desired group, and add an additional call to productCommon.pageDetail. The call arguments are Chart Title, Alias from above, and the tested URL. Ensure the JSON formatting is correct, the easiest way is to simply copy/paste from another line. A sample MR is available here. Assign both MR's to a maintainer. After they are merged, the stage's Grafana dashboard will be automatically updated. A video walkthrough is available as well.