prometheus-community / prometheus-community/PushProx
Scraping multiple exporters via pushprox
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 811
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
I've looked around to see if there was documentation on this but couldn't find anything concrete with regards to pushprox. One of the suggested approaches would be to use relabel_config which drops everything that doesn't match source_labels... however I'm not sure if the labels is being returned when using the http_sd_configs approach.
Each metric collector will most likely need to be a separate job (to ensure that all targets have the specific metrics for collection) but would it make sense to use relabel_config or maybe implement a filter query parameter on the http://localhost:8080/clients endpoint.
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 reviewing the /clients endpoint and the Prometheus http_sd_configs and relabel_config approaches described in the issue. Done means deciding whether exporter selection should be documented or supported through the endpoint, with the resulting multi-exporter scrape setup clearly specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100