vectordotdev / vectordotdev/vector
New `github_metrics` source
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
I'm opening this to start a broader discussion around plugins and integrations with external services. This idea came about after looking into https://github.com/infinityworks/github-exporter. This is an interesting way to pull data from an API/service on an interval. For this source, specifically, we would pull gauges of star counts, release download counts, repo page view counts, and more.
Open questions:
- Is this better provided as a plugin? And do we want to explore a plugin system?
- #992 is an interesting way to solve this. You could provide a simple
github_statscommand that would expose the metrics data when executed. - #991 is also an interesting way to solve this with the aforementioned Github exporter.
- We could explore a generic
httpsource that polls an endpoint and parses the response.
There are a lot of big questions we need to answer before we can begin work on this.
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
No implementation files or tests are named. Start by reviewing the github-exporter reference and the approaches discussed in issues #992 and #991, then resolve whether this should be a plugin, command, exporter integration, or generic HTTP source. Done means a direction is chosen and the scope for collecting GitHub metrics is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- api, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100