* See the spec and schema details in the discussion here - #103
* This commit introduces outputting JSON log format as default for all the 4 source
to improve the tools experience, interoperability and among the initial steps of making
the tool fit well with other log analysis tools and platforms like Azure Monitor, ELK, etc.
* Refactor Log File Monitor
- moved log directory handle to utilities file
- moved create event lgoic and error handling to utilities file
- created an enqueue events function to centralize lock acquisition and releases plus filter out events by file name before adding them to the queue
- (fix) only read sub directory changes when include subfolders is true
- (fix) handle file monitor initialization logic bugs
* first commit
* resolve linter warnings
* move function to another class and create a unit test for OpenConfigFile function
* add unit test and move open config file to configfileparser class
* amend unit test
* amend unit test
* add unit test and centralize logger settings
* shorten line
* un-do linter issue
* Change SAL Annotation
* amend unit test
* fix annotation
* add utility file
* remove un-necessary line of code
Co-authored-by: Charity Kathure <ckathure@microsoft.com>
* config file parser typo fixes
* fixed test typo
* addded an extra quoatation
* reverting back because of tests breaks
* remove unnecessary escape
Co-authored-by: Bob Sira <Bob.Sira@microsoft.com>
Co-authored-by: Charity Kathure <ckathure@microsoft.com>
Co-authored-by: Charity Kathure <ckathure@microsoft.com>
fixes#23
The log file messages only contain the contents of the log files with no indication of the source of the content. This makes it hard to know where these messages are coming from. (Issue: #23 )
Some changes are required to include the file names when displaying contents of log files.
In the case of event logs, the message source is indicated in the Channel tag (application / system):
* update windows build environment
* use windows 2019 build agent
* Update azure-pipelines.yml for Azure Pipelines
* use windows-2019 image
* rerun failed tempts to catch transient failures
* update windows sdk version
* update to windows 2022 build agent and 10.0 sdk
* revert to Windows 2019 agent
* add x86 build job
* fix build platform
* restore component governance task
* update readme build status badge
Co-authored-by: Ian King'ori <iakingor@microsoft.com>
Charity Kathure
Tina Murimi
Anthony Nandaa
Ian King'ori
Bob Sira
Alexander Gama Espinosa
Manoj Kadam