grafana/loki

EKS Mixed Cluster (Linux, Windows) - Log Collection Not Displaying from Windows Nodes

Open

#12,215 opened on Mar 14, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (28,187 stars) (3,997 forks)batch import
area/windowshelp wanted

Description

Everything seems to be fine on startup: image

promtail log: image

The Windows service name can be read in grafana, but the logs cannot be received. image

It is also correct to check the reading position through the promtail log, but loki or grafana just did not collect it.

Ask for help

Contributor guide

Tech stack
gokubernetesaws
Domain
observability
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Basic knowledge of KubernetesFamiliarity with promtailUnderstanding of Windows container logging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate promtail configuration for Windows nodes in EKS. Check if promtail's Windows journal or file target is correctly configured. Review the user's promtail logs to see if there are any errors related to Windows log collection. Test with a simple Windows node setup to reproduce the issue. Consider differences in log paths between Linux and Windows containers. Look at existing promtail Windows documentation or issues. The user mentions service names are visible but logs not received; this may indicate a parsing or shipping issue rather than a discovery issue.