Support JSON logging format in operator - #391
Open
ivanauth wants to merge 1 commit into
Open
Conversation
ivanauth
force-pushed
the
fix/issue-349-json-logging
branch
from
December 13, 2025 02:19
20e2c42 to
d605fb1
Compare
ivanauth
force-pushed
the
fix/issue-349-json-logging
branch
from
January 8, 2026 22:15
d605fb1 to
b40a844
Compare
ivanauth
force-pushed
the
fix/issue-349-json-logging
branch
from
January 23, 2026 21:52
b40a844 to
b43c193
Compare
miparnisari
reviewed
Aug 26, 2026
Contributor
There was a problem hiding this comment.
was this supposed to be part of this PR ?
Contributor
Author
There was a problem hiding this comment.
No good catch, that was an unrelated commit that got mixed into this branch by mistake.
I've rewritten the branch to contain only the JSON logging change. Dropped from the PR:
examples/alternative-registry/pkg/apis/authzed/v1alpha1/types.gopkg/config/config.go,pkg/config/config_test.gopkg/controller/validate_config.go,pkg/controller/validate_config_test.go- both
authzed.com_spicedbclusters.yamlCRDs
Adds a --log-format flag to the run command, accepting "text" (default) or "json". When json is requested the operator installs a zap-backed logr, producing structured output for log aggregation pipelines. The controller now takes a logger as a parameter rather than constructing one internally, so the configured format is used throughout. Fixes authzed#349
ivanauth
force-pushed
the
fix/issue-349-json-logging
branch
from
August 26, 2026 20:24
4086228 to
aae315b
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
--log-formatflag to support JSON logging outputDescription
This PR adds support for JSON-formatted logs in the SpiceDB Operator, addressing issue #349. By default, the operator uses text-based logging, but operators can now use the
--log-format=jsonflag to enable structured JSON logging.Changes
--log-formatflag to theruncommand with validationTesting
Backward Compatibility
Fixes #349