Instrument CRUD operations for work item designs
What does this MR do and why?
Now that we've shipped the work items tracking service, this MR instruments the event tracking for creating, updating, and deleting designs on issues.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
-
In the terminal, run
bin/rails runner scripts/internal_events/monitor.rb work_item_move work_item_design_create work_item_design_destroy work_item_design_updateto monitor these events in your local gdk -
On an issue, add a design by uploading some image
-
Upload a different image of the same name + file extension to trigger an update to the design
-
Archive the design (yes in the UI you archive it, the tracking labels it as "destroy" but it's semantically similar and the service class is destroy)
-
You should see in the terminal that you ran the monitor script in that all 3 events were captured, and the relevant metrics were incremented
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #579672
