Track GDK startup time in Remote Development workspace via telemetry
What does this merge request do and why?
This MR tracks GDK startup time in Remote Development workspace via telemetry.
Related to #2028 (closed)
How to set up and validate locally
-
Open new workspace.
-
Run
git checkout 1986-use-telemetry-for-remote-development-workspace
. -
Run
support/gitlab-remote-development/setup_workspace.rb
.=> GitLab available at http://10.20.0.33:3000. => - Ruby: ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-linux]. => - Node.js: v18.17.0. Total Duration: 17 minutes and 59 seconds. Execution times for each function: configure_gdk: 10 seconds check_inotify: 0 seconds clone_gitlab: 201 seconds copy_items_from_bootstrap: 27 seconds reconfigure_and_migrate: 148 seconds update_gdk: 687 seconds restart_gdk: 6 seconds Success! You can access your GDK here: https://3000-workspace-73241-11762197-lzylgw.workspaces.gitlab.dev Would you like to send the duration data? (yes/no): yes ℹ️ A backup of 'gdk.yml' has been made at '.backups/gdk.yml.20240109030158'.
Also, we can see that the
Finish setup-workspace
event is successfully tracked in the dashboard: https://gitlab.com/gitlab-org/developer-relations/contributor-success/lee-testing/product-analytics-test/-/analytics/dashboards/my_dashboard?date_range_option=last_7_days
Impacted categories
The following categories relate to this merge request:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.
Merge request checklist
-
This change is backward compatible. If not, please include steps to communicate to our users. -
Tests added for new functionality. If not, please raise an issue to follow-up. -
Documentation added/updated, if needed. -
Announcement added, if change is notable. -
gdk doctor
test added, if needed. -
Add the ~highlight
label if this MR should be included in theCHANGELOG.md
.
Edited by Nao Hashizume