feat: add stdout audit logger for log aggregator integration #17914
+621
−14
Conversation
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
d-bytebase
reviewed
Oct 30, 2025
| // Whether the server is running in a docker container. | ||
| IsDocker bool | ||
| // AuditLogStdout enables audit logging to stdout in structured JSON format | ||
| AuditLogStdout bool |
There was a problem hiding this comment.
A setting in
bytebase/proto/v1/v1/setting_service.proto
Line 184 in 7bfa287
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.
Implements JSON-formatted audit logging to stdout for ingestion by log aggregators (Splunk, ELK, Datadog, Loki).
Key features:
Enable with
--audit-log-stdoutflag (disabled by default).Database remains source of truth - stdout failures log warnings but don't block API requests.