Log Monitor Version 2.2.0

LogMonitor v2.2.0

What's New

JSON Configuration Parser Rewrite

The configuration file parser has been rewritten to use nlohmann/json (v3.12.0), replacing the previous Boost.JSON implementation. This removes the Boost dependency, reduces binary size, and simplifies the build.

New AKS / IIS Example

Added a complete iis-logmonitor example for running LogMonitor with IIS on Azure Kubernetes Service, including deployment manifests and documentation.

Bug Fixes

• Fixed incorrect default value for eventFormatMultiLine (was false, should be true)
• Fixed waitInSeconds not being parsed for File log sources (was always using the 300s default)
• Fixed boolean config attributes being stored as strings internally, causing startAtOldestRecord and eventFormatMultiLine to always read as false
• Fixed optional channel level field causing parse failure when omitted (now correctly defaults to Error)
• Fixed invalid log sources causing the entire config to be rejected — invalid sources are now skipped and valid ones are kept
• Fixed path traversal vulnerability in the /Config command-line argument
• Fixed unnecessary error log spam for ERROR_NOT_SUPPORTED cases
• Fixed %s format specifier for narrow strings in ETW monitor error logging

Documentation

• Documented the missing EventSource field in the configuration reference

Build & CI

• Added nlohmann-json vcpkg install step to Azure DevOps pipeline (x64 and x86)
• Added nlohmann-json vcpkg install step to GitHub Actions SDL compliance pipeline
• Added JsonProcessor unit tests covering case-insensitive key matching, optional field defaults, waitInSeconds parsing, and invalid source resilience
• Fixed linker error in VS test project build (LNK2001 for ReadConfigFile)

Dependencies

• Added: nlohmann/json 3.12.0 (via vcpkg)
• Removed: Boost.JSON

Full Changelog: v2.2.0...v2.2.0

Contributors:

• Charity Kathure
• Bob Sira

Log Monitor Version 2.1.3

This release brings the following improvements:

• Fixes JSON parser to correctly handle numeric values (#217)

Contributors:

• Bob Sira

Log Monitor Version 2.1.2

This release brings the following improvements:

• Fixes LogMonitor crashes wrapped process on log line longer than 4000 characters bug (#212)
• Documentation update: Added security advisory for config file

Contributors:

• CharityKathure
• profnandaa

Log Monitor Version 2.1.1

This release brings the following improvements:

• Reverts the modification to explicitly write wide string characters to the console to fix the log output issue in Log Monitor 2.1.0
• Sets up GitHub code scanning
• Addresses security vulnerability alerts identified by GitHub code scanning

Contributors:

• Bob Sira
• CharityKathure
• Ian Kingori
• Tina Murimi

Log Monitor Version 2.1.0

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

Log Monitor Version 2.0.2

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

Log Monitor Version 2.0.1

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🎉

Log Monitor Version 2.1.0-rc0

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

Log Monitor Version 2.0

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

Log Monitor Version 2.0-rc0

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