Upgrade to Log4J2 and added logging for Cosmos DB request Diagnostics #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Upgrade to Log4J2 and added logging for Cosmos DB request Diagnostics
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pulling changes from "request_diagnostics" branch.
Upgrade to Log4J2 to leverage filers with markers to separate out request diagnostics based on the Cosmos DB operation performed.
The location of the log files is in a directory called "cosmos_client_diagnostic_logs" under "/tmp" directory. Here you will find folders "read", "query", "patch" and "create". This location and additional configuration can be done by the log4j2.xml file in the resource folder of Cosmos DB binding project.
Diagnostic logging for query operation is not enabled yet.