microsoft / microsoft/windows-container-tools

[BUG]Logs stop being sent to the standard output log for Event Viewer Logs

Open
#194 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
277
Forks
77
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
Logs stop being sent to the standard output log for Event Viewer Logs, if I go into the pod using kubectl exec I can get log entries from the event log that have not been sent to the standard output by LogMonitor.exe.
We're not going to upgrade to the latest LogMonitor.exe until the following blocker is fixed: https://github.com/microsoft/windows-container-tools/issues/187 so we can't test if this happens in the latest version of the tool.

To Reproduce
Send messages into the Event Viewer log of the configuration you've defined in the Log Monitor configuration file

Expected behavior
All logs should be read and sent to the standard output

Screenshots
NA

Configuration
-Tool: LogMonitor.exe
-Version: 2.0.2

Additional context
Configuration file:

{
    "LogConfig":  {
                      "sources":  [
                                      {
                                          "eventFormatMultiLine":  false,
                                          "channels":  [
                                                           {
                                                               "level":  "error",
                                                               "name":  "system"
                                                           },
                                                           {
                                                               "level":  "Verbose",
                                                               "name":  "Epicor ICE Task Agent Service"
                                                           }
                                                       ],
                                          "type":  "EventLog",
                                          "startAtOldestRecord":  true
                                      },
                                      {
                                          "filter":  "*.log",
                                          "directory":  "c:\\inetpub\\logs",
                                          "includeSubdirectories":  true,
                                          "type":  "File"
                                      }
                                  ]
                  }
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with LogMonitor.exe 2.0.2 and the EventLog configuration shown in the issue, then trace the EventLog source and standard-output handling. Done means all matching Event Viewer records, including those available through kubectl exec, are sent to standard output.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
observability, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.