fix: Switch default logging to JSON (issue: 20897) #21656
+182
−183
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.
Closes #20897
This change updates the default log format in
util/log
fromtext
tojson
. It will be used for ArgoCD v3.0.JSON logging is preferred because it produces structured logs, which are easier to parse and analyze with tools like Datadog and OpenTelemetry (Otel). These integrations rely on structured log formats to extract meaningful data and streamline observability workflows. Switching from
json
tojson
ensures better compatibility with modern logging and monitoring solutions.Checklist: