prometheus-community / prometheus-community/PushProx

Scrap control plane

Open
#162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
811
Forks
154
PR merge metrics
No merged PRs in 30d

Description

I have a Rancher installation and the entire Kube-Prometheus stack was installed from outside and not through the Rancher console, because the monitoring stack was consuming a lot of resources through Rancher. Anyway, I installed the stack and was able to monitor everything, except for some components such as kube-scheduler, kube-proxy and kubecontrollermanager. I saw that Rancher uses pushprox to monitor these components. I even found a chart that Rancher itself provides, but I didn't understand how to monitor these components using the same helm chart and even seeing the official documentation here, I found it very superficial. can anybody help me?

Contributor guide

No contributing guide indexed for this repository

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

Start with the official PushProx documentation and the Helm chart provided by Rancher, then compare their guidance with the kube-scheduler, kube-proxy, and kube-controller-manager monitoring requirements described here. Done means documenting a clear installation and configuration path for monitoring those components outside the Rancher console.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, helm, kubernetes
Domain
devops, observability-sre
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.