Altinity / Altinity/clickhouse-operator
ServiceMonitor also selects Clickhouse Nodes
@Slach is already working on this.
Since Feb 27, 2024.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Hey,
i noticed when i use the ServiceMonitor in the HelmChart also the clickhouse nodes are selected. So Prometheus tries to scrape them on Port 8888 and Port 9999 which leads to an connection refused.
As far as i understand it is not intentend to scrape the Clickhouse Nodes directly but the clickhouse-operator which provides the metrics. My dashboard is already filled with the correct metrics but i get TargetDown Alerts which i want to fix.
I think it is because the Clickhouse Nodes is:
spec:
endpoints:
- port: clickhouse-metrics
- port: operator-metrics
selector:
matchLabels:
app.kubernetes.io/instance: clickhouse
app.kubernetes.io/name: altinity-clickhouse-operator
i think the issue is that the Operator and the Clickhouse Services both have the same labels and therefore get picked up by the ServiceMonitor.
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.
Assessment
This issue has not been assessed yet.