Add more initializer-related info to /insights API

[geropl]

Description

This PR introduces the following shape on the ListWorkspaceSessionsApi:

  message Metrics {
    [...]

    // initializer_metrics are all metrics exported from the content initializer on workspace start
    InitializerMetrics initializer_metrics = 3;
  }

  // Add these new message definitions
  message InitializerMetric {
    // Duration in nanoseconds (standard protobuf duration)
    google.protobuf.Duration duration = 1;

    // Size in bytes
    uint64 size = 2;
  }

  message InitializerMetrics {
    // Git contains metrics for the git initializer step
    InitializerMetric git = 1;

    // FileDownload contains metrics for the file download initializer step
    InitializerMetric file_download = 2;

    // Snapshot contains metrics for the snapshot initializer step
    // This used for workspaces started from snapshots.
    InitializerMetric snapshot = 3;

    // Backup contains metrics for the backup initializer step
    InitializerMetric backup = 4;

    // Prebuild contains metrics for the prebuild initializer step
    InitializerMetric prebuild = 5;

    // Composite contains metrics for the composite initializer step
    InitializerMetric composite = 6;
  }

It has basically the same content as the "metrics" shape "ready" in the workspace's ready file.

Example CSV: gitpod-sessions-supercorp-20250218-20250225.csv

Related Issue(s)

Fixes CLC-1052

How to test

• login: https://gpl-1052-m31215eec26.preview.gitpod-dev.com/workspaces
• visit /insights, and Download the CSV
• (optional) start more/different workspace, and observe the result

Documentation

Preview status

gitpod:summary

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[geropl]

@iQQBot Would be awesome if you could help review all the workspace/ws-daemon parts of this PR, with a focus on how these changes could fail/block a workspaces start, which should never be the case. 🙏

[filiptronicek]

Left some comments, including blocking ones. Continuing with my review in the bg...

[geropl]

Redeploying the preview...

[geropl]

Done @filiptronicek

fromBackup is filled now 💪

[filiptronicek]

Awesome sauce! Looks great

[filiptronicek]

Tested and reviewed (although I just skimmed over the ws-daemon changes). Looks amazing!

wrt the initializer types: I managed to catch 'em all, so I'm satisfied ;).

[filiptronicek]

out of curiousity: was waiting the 1s the fix to your problems with the file being empty?

[geropl]

@iQQBot Waiting for your feedback now 👍

[iQQBot]

Code LGTM, Just curious, why use the fd method to transfer data? Don't we already have file records in filepath.Join(ws.Location, ".gitpod/ready")? We can also directly read this file.

[geropl]

/unhold

[geropl]

Just curious, why use the fd method to transfer data? Don't we already have file records in filepath.Join(ws.Location, ".gitpod/ready")? We can also directly read this file.

True! I wanted to to decouple both aspects, and found we already have that .ExtraFiles mechanism, so happily used that. 🙂