vectordotdev/vector

A high-performance observability data pipeline.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 7 minutes ago
Added to GitGenius on September 2nd, 2026
Created on August 27th, 2018
Open Issues & Pull Requests: 2,515 (+0)
GitHub issues: Enabled
Number of forks: 2,272
Total Stargazers: 22,520 (+1)
Total Subscribers: 153 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.9 hours
Mean response time: 67.7 days
90th percentile: 182.1 days
Tracked items: 6,280

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 92% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "domain: observability" is answered fastest, typically in about 4 hours, while "have: should" waits about 31 hours. 53% of tracked open issues have had no activity in three months. Only 1% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,833
New in 7 days: 6
Closed in 7 days: 10
Avg open age: 1,281 days
Stale 30+ days: 1,741
Stale 90+ days: 1,533

Recent activity

Opened in 7 days: 5
Closed in 7 days: 8
Comments in 7 days: 6
Events in 7 days: 12

Top labels

  • domain: vrl (495)
  • domain: observability (373)
  • domain: config (360)
  • domain: external docs (323)
  • needs: approval (310)
  • have: should (268)
  • domain: performance (239)
  • source: file (198)

Detailed Description

Vector is a high-performance observability data pipeline that collects, transforms, and routes logs, metrics, and traces to any vendor.

Vector addresses the challenge of managing observability data across multiple vendors and preventing vendor lock-in. It works by acting as either an agent deployed on individual hosts or an aggregator that centralizes data collection, allowing teams to ingest data from any source, apply transformations, and route it to multiple destinations. This approach gives organizations control over their observability data rather than being constrained by vendor-specific tooling, enabling cost reduction through intelligent routing and data enrichment at the source.

Teams should adopt Vector if they operate multi-vendor observability stacks, need to reduce observability costs, or want to transition between vendors without disrupting existing workflows. It suits organizations that process significant data volumes and need reliable, performant data handling. The tool is particularly valuable for consolidating multiple specialized agents into a single unified platform that handles logs, metrics, and traces together.

The project maintains active development with regular contributions across its codebase. The tool is written in Rust, emphasizing reliability as a core design principle. Vector is maintained by a dedicated community engineering team and has established clear policies covering code of conduct, contributing guidelines, security practices, versioning, and release management.