Skip to content

Capture Windows cloud-init log (C:\debuginit.txt) in telemetry - #85

Open
PrashantRaj18198 wants to merge 1 commit into
mainfrom
fix/capture-windows-cloudinit-log
Open

Capture Windows cloud-init log (C:\debuginit.txt) in telemetry#85
PrashantRaj18198 wants to merge 1 commit into
mainfrom
fix/capture-windows-cloudinit-log

Conversation

@PrashantRaj18198

Copy link
Copy Markdown
Member

Why

While debugging the SonarSource rate-limit incident (runners stuck ALLOCATED because the job-started prehook never fires on their Windows BYOC runners), the investigation dead-ended: the cloud-init phase writes settings.json (including ACTIONS_RUNNER_HOOK_JOB_STARTED) and logs every step to C:\debuginit.txt — but that file is not shipped by the telemetry collector, so we cannot see whether the config write or the setup scripts (020_setup_warp_agent.vm.ps1) succeeded on customer VMs.

What

  • New filelog/cloudinit receiver (Windows only) tailing C:\debuginit.txt, wired into the logs pipeline with log.type: cloud_init.
  • start_at: beginning — cloud-init completes before the collector service starts, so end would capture nothing.
  • Optional by construction: filelog with a non-existent path simply matches nothing; images without the file are unaffected.

Verified the template renders to valid YAML for both windows and linux.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WYUvqHtPgFTcXebxgvadxn

Optional: filelog matches nothing when the file is absent. start_at beginning
because cloud-init finishes before the collector starts.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WYUvqHtPgFTcXebxgvadxn
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant