prometheus-community / prometheus-community/PushProx
How to scrape metrics from not /metrics endpoint?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 811
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
Hey,
I implemented prometheus-pve-exporter in my proxmox server. But my entire monitoring is run in external cloud configuration. To provide one endpoint to scrape all metrics from all services run in proxmox in decided to use PushProx. The all configuration works quite well.. but I realised that when I use this this tool then I can not scrape metrics from extra endpoint /pve but i must use only endpoint /metrics.
It is possible to configure more endpoints to scrape metrics?
- job_name: "proxmox"
proxy_url: <<http://A.B.C.D:XXX>>
metrics_path: /metrics
...
static_configs:
- targets: [proxmox.local:9221]
when I tried change metrics_path to use /pve then it not works.. any Idea how I can fix this issue?
Contributor guide
No contributing guide indexed for this repository
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 PushProx setup with the Prometheus scrape configuration shown, comparing metrics_path: /metrics with /pve. Trace how PushProx handles the target path and confirm whether additional endpoints are supported. Done means establishing the supported behavior and documenting or implementing the required configuration for scraping /pve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- networking, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100