Prometheus Screapes to Multiple Ports Of Pods #9677
Unanswered
biswa-r-singh
asked this question in
Q&A
Replies: 1 comment
-
It seems you have a typo: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
PROMETHEUS SCRAPES ON MULTIPLE PORTS OF POD FOR UNKNOWN REASON. Please see the details of the issue.
Prometheus Scrape Configuration
Pod Definition
tcptrack command output in testpod
10.198.22.240:51258 10.198.40.143:7079 CLOSED 10s 0 B/s
10.198.22.240:50354 10.198.40.143:7079 CLOSED 40s 0 B/s
10.198.22.240:33152 10.198.40.143:4040 ESTABLISHED 2s 0 B/s
10.198.22.240:47726 10.198.40.143:8090 ESTABLISHED 9s 0 B/s
10.198.22.240 = prometheus pod ip
10.198.40.143 = testpod ip
Issue
Though the scrape config is expected to scrape on port 8090. I see prometheus tries to initiate scrape on ports like 7079, 4040, etc on
the test pod. Why its happening? Any insight?
Beta Was this translation helpful? Give feedback.
All reactions