Vector

Vector is an open-source observability pipeline that collects, transforms, and routes logs, metrics, and traces.

  • Cloud
  • Databases
  • Monitoring & Logging
  • Productivity
  • Tools & Utilities
Vector is an open-source observability pipeline that collects, transforms, and routes logs, metrics, and traces. It runs as an agent or aggregator, letting self-hosted teams send telemetry to any backend and transform it with built-in rules. Use it when you need reliable, high-performance telemetry routing without tying your setup to a single vendor.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

85/100 Excellent

Maintained
100last commit 23 days ago
Popular
8722,778 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 9 days ago

GitHub stars
22,778
Open issues
2564
Last commit
2026-10-29
Latest release
v0.61.0
License
MPL-2.0
Activity
rising

Checked 23 days ago - source: GitHub (vectordotdev/vector)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 80 MB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Check VRL code before starting Before starting Vector, review any VRL (Vector Remap Language) code in your transforms, because a small mistake can stop log events from being shaped and sent onward. A working transform helps you confirm your pipeline is moving data correctly. source
  • Keep bad log lines from breaking parsing If you parse custom log lines into fields, add ?? fallbacks so missing or badly formatted pieces do not stop Vector from processing the rest. This helps one odd log line avoid breaking your whole setup. source
  • Prepare configuration before first start Vector has no default configuration. Create vector.yaml in the configured directory before first start. If using the docker_logs source to collect logs from other containers, keep the Docker socket path available. source

Fetched 49 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Vector need a configuration file before the first start?

Yes. Vector has no default configuration, so create a vector.yaml file in the configured directory before starting it.

What should I check in Vector Remap Language code before starting Vector?

Review the VRL code in transforms because a small mistake can stop log events from being shaped and sent onward. Add ?? fallbacks when parsing custom log lines so missing or badly formatted pieces do not stop processing.

Can Vector deploy as a daemon, sidecar, or aggregator?

Yes, Vector can deploy as a daemon, sidecar, or aggregator.

Can Vector be used to change telemetry backends without disrupting existing workflows?

Yes, it can be used to transition vendors without disrupting workflows.

Answers sourced from github.com, vector.dev, vector.dev

Community

Collected 4 days ago - public community threads