Fix log pipeline - populate logs into kusto #170
Draft
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.
Issue describing the changes in this PR
With the current logging logic in the SDK, the logs are not recorded anywhere, causing the logs in the SDK to be meaningless.
This PR updates the current Java Util Logger with
FunctionKustoHandler
, a customizedjava.util.logging.Handler
that will stream the logs into kusto table. The picture below shows an example.Pull request checklist
CHANGELOG.md
Additional information
Additional PR information