Altinity / Altinity/clickhouse-operator

Structured Logging for Operator

Open
#1,516 3 comments 15 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
2.6k
Forks
574
Avg merge
8d 6h
Merged PRs (30d)
6

Description

Can the operator be configured such that it logs in a structured (JSON) format?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by tracing the operator's current logging setup and configuration surface; completion should define and verify a configurable JSON output format, but the issue does not specify the required fields or validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.