Service and ServiceMonitor target unused exporter port (8888)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, kubernetes, prometheus
- Domain
- devops, observability
Research direction
Start with the ServiceMonitor and Service configurations shown in the issue, then compare their target ports with the operator startup logs. Verify which metrics endpoints are exposed and scraped; done means the configuration targets only active ports and the role of port 8080 is documented or resolved.
Written by the indexing model from the issue text.
Description
The operator's ServiceMonitor configuration targets two ports (ch-metrics:8888 and op-metrics:9999), but the operator pod only exposes port 9999 if exporter is disabled
ServiceMonitor:
spec:
endpoints:
- interval: 30s
port: ch-metrics
- interval: 30s
port: op-metrics
same for the Service:
ports:
- name: ch-metrics
port: 8888
protocol: TCP
targetPort: 8888
- name: op-metrics
port: 9999
protocol: TCP
targetPort: 9999
Expected Behavior:
The ServiceMonitor should only target the actively used operator metrics port (9999)
also there are those 2 log line on operator startup:
log 1: start serving metrics at: :9999/metrics
log 2: 2025-09-29T13:05:50Z INFO controller-runtime.metrics Metrics server is starting to listen {"addr": ":8080"}
is there a reason 8080 is not scraped?
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 577
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Altinity/clickhouse-operator
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Altinity/clickhouse-operator#2093 ·
Maintainers usually reply within 2 days
-
[Regression / Discussion] Loss of hot-reloaded password rotation after removal of k8s_secret_* in 0.27.4Possibly taken @sunsingerus claimed this 1 day ago. Openplanned for review
Difficulty 5/5 Over a week Newbie friendliness 38/100
Altinity/clickhouse-operator#2092 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Altinity/clickhouse-operator#2089 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
Altinity/clickhouse-operator#2064 · 3 comments ·
Maintainers usually reply within 2 days
-
big deployment planned for review
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Altinity/clickhouse-operator#2063 ·
Maintainers usually reply within 2 days
All issues in Altinity/clickhouse-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
shukiv/jabali-panel#2029 ·
Maintainers usually reply within 1 day
-
[submenu] nil issue on ubuntu 26.04Possibly taken @egoist claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prime-radiant-inc/evener#3873 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
v2fly/domain-list-community#4127 ·
Maintainers usually reply within 2 days
-
extract_llm_sweep / cache_aware_summarizer prefix ask 400s when thinking.budget_tokens exceeds PrefixAskMaxTokensPossibly taken @amiddavid claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
rossoctl/context-guru#405 ·
Maintainers usually reply within 1 day