worker-ready-tracing

Trace Windows VM startup latency by collecting and aligning markers from worker-manager provisioning through in-VM startup to the first eligible task claim. The Skill uses tc-logview, Papertrail, Splunk, and Yardstick to pinpoint slow steps across host and guest boundaries.

Azure Windows VM readiness delays can be diagnosed by comparing azure-vm-write timings against in-VM Puppet and Start-WorkerRunner phases. The Skill surfaces timestamps across provisioning and startup to identify which lifecycle step is slow.

Correlate worker-manager logs with in-VM startup logs by collecting WORKER_METRICS from Papertrail, Azure activity logs from Splunk, and pool metrics from Yardstick. The Skill aligns these multi-source markers to produce a unified lifecycle timeline.

Yes, you can measure end-to-end readiness latency from Azure VM provisioning to workerReady. The Skill computes durations between lifecycle markers and prints structured timelines showing each phase from VM creation to first task claim.

You need a worker-id, which is the Azure VM name, and a time window to generate the lifecycle trace. The Skill then queries tc-logview, Papertrail, Splunk, and in-VM logs to collect and align the relevant readiness markers.

Yes, it traces generic-worker startup phases on Windows by parsing in-VM logs and worker-manager events. The Skill identifies boot and recovery cycles to diagnose latency causes specific to Windows Taskcluster workers.