Skip to content
master
Switch branches/tags
Code

Latest commit

* Slim unused dependencies from the project

This commit enables two global lints: `unused_extern_crates` and
`unused_crate_dependencies`. The remainder of the changes chase what those lints
flagged. This should, ideally, mean we generate less dependabot updates, require
slightly less build time. I have not applied these lints to sub-crates.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* criterion ding

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* incremental progress on cargo-hack

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* more incremental progress

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* further incremental progress

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* slim features

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* more incremental progress

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* fix shutdown tests

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* dinged by rusoto_es, assert_cmd

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* less dings

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* Back off unused_crate_dependencies

While this is an interesting lint it's overly strict, at least for the state of
the root crate. Our dev-dependencies get flagged quite a bit and, while we do
have inconsistent use of them, that I'm less concerned about. To resolve we'd
need to pull these into `src/lib.rs` as _ imports.

I do think the basic idea is a good one and can apply to sub-crates well
enough. Feasible to pick this back up after we slim feature flags out of the
project.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* indoc dings

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* more dings

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* remove dev-dependency dance

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* warp is non-optional

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* bollard non-optional

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* more reqwest/json for es

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* reqwest dings

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* value ding

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>
7556dc3

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time

Quickstart  •   Docs  •   Guides  •   Integrations  •   Chat  •   Download

Vector

What is Vector?

Vector is a high-performance, end-to-end (agent & aggregator) observability data pipeline that puts you in control of your observability data. Collect, transform, and route all your logs, metrics, and traces to any vendors you want today and any other vendors you may want tomorrow. Vector enables dramatic cost reduction, novel data enrichment, and data security where you need it, not where it is most convenient for your vendors. Additionally, it is open source and up to 10x faster than every alternative in the space.

To get started, follow our quickstart guide or install Vector.

Principles

  • Reliable - Built in Rust, Vector's primary design goal is reliability.
  • End-to-end - Deploys as an agent or aggregator. Vector is a complete platform.
  • Unified - Logs, metrics, and traces (coming soon). One tool for all of your data.

Use cases

  • Reduce total observability costs.
  • Transition vendors without disrupting workflows.
  • Enhance data quality and improve insights.
  • Consolidate agents and eliminate agent fatigue.
  • Improve overall observability performance and reliability.

Community

  • Vector is relied on by startups and enterprises like Atlassian, T-Mobile, Comcast, Zendesk, Discord, Fastly, CVS, Trivago, Tuple, Douban, Visa, Mambu, Blockfi, Claranet, Instacart, Forcepoint, and many more.
  • Vector is downloaded over 100,000 times per day.
  • Vector's largest user processes over 30TB daily.
  • Vector has over 100 contributors and growing.

Documentation

About

Setup

Reference

Administration

Resources

Comparisons

Performance

The following performance tests demonstrate baseline performance between common protocols with the exception of the Regex Parsing test.

Test Vector Filebeat FluentBit FluentD Logstash SplunkUF SplunkHF
TCP to Blackhole 86mib/s n/a 64.4mib/s 27.7mib/s 40.6mib/s n/a n/a
File to TCP 76.7mib/s 7.8mib/s 35mib/s 26.1mib/s 3.1mib/s 40.1mib/s 39mib/s
Regex Parsing 13.2mib/s n/a 20.5mib/s 2.6mib/s 4.6mib/s n/a 7.8mib/s
TCP to HTTP 26.7mib/s n/a 19.6mib/s <1mib/s 2.7mib/s n/a n/a
TCP to TCP 69.9mib/s 5mib/s 67.1mib/s 3.9mib/s 10mib/s 70.4mib/s 7.6mib/s

To learn more about our performance tests, please see the Vector test harness.

Correctness

The following correctness tests are not exhaustive, but they demonstrate fundamental differences in quality and attention to detail:

Test Vector Filebeat FluentBit FluentD Logstash Splunk UF Splunk HF
Disk Buffer Persistence
File Rotate (create)
File Rotate (copytruncate)
File Truncation
Process (SIGHUP)
JSON (wrapped)

To learn more about our correctness tests, please see the Vector test harness.

Features

Vector is an end-to-end, unified, open data platform.

Vector Beats Fluentbit Fluentd Logstash Splunk UF Splunk HF
End-to-end
Agent
Aggregator
Unified
Logs
Metrics
Traces 🚧
Open
Open-source
Vendor-neutral
Reliability
Memory-safe
Delivery guarantees
Multi-core

= Not interoperable, metrics are represented as structured logs


Developed with ❤️ by Datadog - Security Policy - Privacy Policy