vectordotdev / vectordotdev/vector
Healthcheck/Uptime source
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
It was suggested in our community chat that Vector could support generating its own metrics by probing HTTP services and recording response time, status codes, etc.
Similar to the Prometheus source, it would make HTTP requests to a configurable set of endpoints on a configurable interval and forward metrics about the outcome of those requests.
We have had other requests for an HTTP client source that would work this way but return the response data itself instead of metrics. It's likely that we could make this the same source and allow users to configure if they'd like metrics or data or both.
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 by examining the existing Prometheus source as the closest reference. Define how configurable HTTP endpoints, polling intervals, response metrics, and optional response data should be represented. Done means the source supports the requested healthcheck behavior and clearly specifies whether it emits metrics, response data, or both.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100