Skip to content

[docs] adds troubleshooting instructions for windows-exporter logs #4530

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
openshift-merge-bot merged 1 commit into from
Sep 22, 2026
Merged

[docs] adds troubleshooting instructions for windows-exporter logs #4530

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/TROUBLESHOOTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,8 +99,8 @@ tracing processes during troubleshooting:
running processes, `kube-log-runner.exe` is the visible parent, and the actual
service binary is its child. Log files are under `C:\var\log\<service>\`.

- WICD service (`windows-instance-config-daemon`) however, runs as a standalone process with no
`kube-log-runner` wrapper. It writes and rotates its own log files directly under `C:\var\log\wicd\`.
- WICD service (`windows-instance-config-daemon`), and windows-exporter (`windows-exporter`) however, run as standalone processes with no
`kube-log-runner` wrapper. They write their own log files directly under `C:\var\log\wicd\` and `C:\var\log\windows_exporter\windows_exporter.log` respectively.

See [Logging architecture: WICD vs managed services](log-rotation-managed-services.md#logging-architecture-wicd-vs-managed-services)
for the full explanation of why this difference exists.
Expand All @@ -120,6 +120,7 @@ ip-10-0-138-252.us-east-2.compute.internal containers/
ip-10-0-138-252.us-east-2.compute.internal hybrid-overlay/
ip-10-0-138-252.us-east-2.compute.internal kube-proxy/
ip-10-0-138-252.us-east-2.compute.internal kubelet/
ip-10-0-138-252.us-east-2.compute.internal windows_exporter/
ip-10-0-138-252.us-east-2.compute.internal pods/
```
You can now list files in the directories using the same command and view the individual log files. For example to view
Expand Down