Closed CharityKathure closed 1 month ago
As for the PR base, reason we're going for release/2.2
other than main
?
@profnandaa main has only the JSON formatting option (there is no log formatting option in config). release/2.2 branch has the JSON
+ XML
+ Custom
logging work that is in the log monitor rc2.1.0.
This issue will only be noted in rc2.1.0.
@profnandaa main has only the JSON formatting option (there is no log formatting option in config). release/2.2 branch has the
JSON
+XML
+Custom
logging work that is in the log monitor rc2.1.0.This issue will only be noted in rc2.1.0.
Got it. I think after the merge we can discuss switching the branches so that the code currently shipping can be in main
and then the legacy v1 code can be in a v1 branch.
/cc. @iankingori @tinamor
Addressing issue: https://github.com/microsoft/windows-container-tools/issues/171
Issue Description:
Log Monitor allows users to specify the log format (Custom, JSON, or XML) for ETW, Event logs, and File logs through the respective sections in the config.json file.
However, in the case of process monitor logs, whose specifications are not captured in the config file, the logs should default to JSON unless the user specifies XML as the desired log format.
In the current implementation (in rc2.1.0), the default log format is XML unless JSON is specified. This is why when rc2.1.0 users specify
"logFormat": "custom"
the process monitor logs default to XML format.For example:![image](https://github.com/microsoft/windows-container-tools/assets/28774968/f20ac559-2bf5-4935-8e23-a6a80b6c7b6a)
This change ensures that the default log format is
JSON