vectordotdev / vectordotdev/vector
Autodiscovery of Prometheus endpoints for scraping
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Feedback from our chat
- 90% of prometheus endpoints require autodiscovery (various orchestration systems like k8s, etc - most used cases) and it's not supported in vector.
- in most of cases it's better to use native collectors (or compatible ones like https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/app/vmagent) and receive benefits - delivery guarantees, deduplication etc. (especially considering that vector native proto does not have delivery guarantees so far)
I tend to agree. This would be a really nice feature for anyone using Prometheus, but it's not easy either :). For reference, here's the Prometheus configuration. Notice all of the cloud settings that enable autodiscovery.
We definitely need to discuss how we can reduce scope of this feature.
/cc @afoninsky
Contributor 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.
Research direction
Start with the issue discussion and the linked Prometheus configuration reference. No files, tests, or entry points are named, and the scope is explicitly still under discussion. Done would require an agreed reduced scope for Prometheus endpoint autodiscovery and corresponding implementation criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100