Altinity / Altinity/clickhouse-operator
No prometheus metrics related to running clickhouse clusters
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
I have a setup where clickhouse-operator running in namespace "mgmt" and multiple clickhouses running across multiple namespaces.
The service clickhouse-operator-service exists and in listening on 8888/TCP and 9999/TCP. A service monitor in running. I can see clickhouse-operator- metrics but no metrics related to clickhouse dbs. I have checked with port forward, and there are no metrics on port 8888. Don't see anything related in logs either.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report against the clickhouse-operator-service endpoints on ports 8888 and 9999, checking the ServiceMonitor and operator logs described in the issue. Determine why metrics for running ClickHouse clusters are absent while operator metrics are available; done means the expected cluster metrics are exposed and collectable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, prometheus
- Domain
- infrastructure, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100