MR Widget Extension Telemetry - `WidgetBrowserPerformance`
What
We need to implement metrics instrumentation around each of the events that widgets in the Widget Extension framework automatically report.
How
Follow the steps documented here.
Note the mention of the --ee
flag.
When
There isn't a huge amount of urgency for this, but it would be nice to have sooner rather than later.
Events that aren't included in metrics are reported as errors by our backend system.
To avoid needing to disable telemetry entirely for widgets that are not instrumented, we should just instrument them all.
Notably, these errors are not causing problems (internal slack link), but they are noisy.
Why
Other than to increase the telemetry information we receive by default from widgets, why this way is because this is how we track metrics with Redis.
Other info
You might find it useful to look at the 4 CE widgets that have already been addressed in the MRs below.
Each was done by following the steps in the documentation linked above.
Issue/MR | Widget | EE? |
---|---|---|
!91831 (merged) | WidgetTestSummary |
|
!93340 (merged) | WidgetTerraform |
|
!93333 (merged) | WidgetCodeQuality |
|
!93232 (merged) | WidgetAccessibility |
|
#368871 (closed) | WidgetSecurityReports |
|
We are here |
WidgetBrowserPerformance |
|
#368873 (closed) | WidgetLicenseCompliance |
|
#368874 | WidgetLoadPerformance |
|
#368875 (closed) | WidgetMetrics |
|
#368876 (closed) | WidgetStatusChecks |