windows-container-tools

This release brings the following improvements:

• The custom Log Format feature is now promoted to a stable release
• Fixes file watcher hanging and improves console write performance
• Resolves log stream delays when a monitored directory does not exist
• Adds the event source name entry in Event Logs
• Adds signal handling for common catastrophic failure signals, ensuring the log monitor exits properly and prevents containers from hanging indefinitely

Contributors:

• Bob Sira
• CharityKathure
• Ian Kingori
• Tina Murimi

This release brings the following improvements:

• Fixes failure in monitoring EventLog in mcr.microsoft.com/dotnet/framework/runtime:4.8-windowsservercore-ltsc2019 with error code 0x6BA.

Contributors:

• Bob Sira

This release brings the following improvements:

• Implement configurable wait time for non existent directory issue
• Include ProviderGuid in Event Monitor error logs
• Fixes file monitor 30 seconds delay bug (#156)
• Fixes File monitor bug failing to monitor files in root directory
• Fixes a versioning bug
• Stability and Quality Improvements
  • Added automated code quality and security checks

Contributors:

• Charity Kathure
• Bob Sira
• Tina Murimi🎉

This release brings the following improvements:

• JSON output as default for the 4 log sources
• New log format (Custom Log format): Custom Log Format
• Configurable log format (Capability to switch between JSON, XML and Custom log formats)
• Stability and Quality Improvements:
  • Formatting for scalar integer property values using TdhFormatProperty
  • Descriptive build scripts
  • Documentation updates
  • ETW Monitor code refactor

Contributors:

• Charity Kathure
• Bob Sira

This release brings the following improvements:

• All monitors, ETW, Process, Events and File now output JSON logs as specified in this schema discussion
• ETW provider name now included in ETW Log Output
• Stability and Quality Improvements:
  • Docs Fix: specify default level as Error for Event Log
  • Fixes a bug where file monitor source tagging skips some log lines

Known Issues:

• Log output format is not configurable, discussions on additional log formats: discussion #123

Contributors:

• kimpanatopimizely
• profnandaa
• CharityKathure
• bobsira

This release brings the following improvements:

• All monitors, ETW, Process, Events and File now output JSON logs as specified in this schema discussion
• ETW provider name now included in ETW Log Output
• Stability and Quality Improvements:
  • Docs Fix: specify default level as Error for Event Log
  • Fixes a bug where file monitor source tagging skips some log lines

Known Issues:

• Process Monitor does not support multi-byte characters: issue #121
• Log output format is not configurable, discussions on additional log formats: discussion #123

Contributors:

• kimpanatopimizely🎉
• profnandaa
• CharityKathure
• bobsira

*🎉 == first time contributors

This release brings the following improvements:

• Adds a feature to tag all log lines from file with their corresponding file names
• Fixes a bug causing stderr and stdout to interleave making log lines unreadable
• Fixes a bug where we track change events in subfolders even when include subfolders is off
• Stability and Quality Improvements:
  • Improved Documentation
  • File Monitor Thread safety improvements

Contributors:

• mloskot🎉
• lucillex 🎉
• profnandaa
• CharityKathure
• bobsira
• iankingori

*🎉 == first time contributors

This release brings the following improvements:

• Added UTF-8 encoding support for STDOUT stream
• Log Monitor will now pass through the exit code of any child process it spawns to caller
• Added x86 Build Support
• Added support for UTF-8 encoded Config Files
• Stability and Quality Improvements:
  • Replaced some deprecated WinAPI methods
  • Updated windows SDK version

Contributors to version 1.2.0:

• ulfaxelssoncab
• pengzhisun
• profnandaa
• CharityKathure
• bobsira
• iankingori

The v1.1 Release of Log Monitor. This release includes a bug fix that allows child processes/apps (i.e. IIS Service Monitor) to shutdown gracefully.

The first release of Log Monitor, a tool for logging with Windows Containers.