Vector Components

Components enable you to collect, transform, and route data with ease

Sources count 43

Collect events from AMQP 0.9.1 compatible brokers like RabbitMQ

Apache Metrics source

Collect metrics from Apache’s HTTPD server

AWS ECS metrics source

aws_ecs_metrics

Collect Docker container stats for tasks running in AWS ECS and AWS Fargate

AWS Kinesis Firehose source

aws_kinesis_firehose

Collect logs from AWS Kinesis Firehose

Collect logs from AWS S3

Collect logs from AWS SQS

Datadog agent source

Receive logs, metrics, and traces collected by a Datadog Agent

Demo Logs source

Generate fake log events, which can be useful for testing and demos

Collect DNS logs from a dnstap-compatible server

Docker logs source

Collect logs from Docker

EventStoreDB metrics source

eventstoredb_metrics

Receive metrics from collected by a EventStoreDB

Collect output from a process running on the host

Collect logs from files

File Descriptor source

file_descriptor

Collect logs from a file descriptor

Collect logs from a Fluentd or Fluent Bit agent

GCP PubSub source

Fetch observability events from GCP’s PubSub messaging system

Heroku Logplex source

Collect logs from Heroku’s Logplex, the router responsible for receiving logs from your Heroku apps

Host metrics source

Collect metric data from the local system

HTTP Client source

Pull observability data from an HTTP server at a configured interval

HTTP Server source

Receive observability data from an HTTP client request

Internal logs source

Expose all log and trace messages emitted by the running Vector instance

Internal metrics source

internal_metrics

Access to the metrics produced by Vector itself and process them in your Vector pipeline

JournalD source

Collect logs from JournalD

Collect observability data from Apache Kafka topics

Kubernetes logs source

kubernetes_logs

Collect logs from Kubernetes Nodes

Logstash source

Collect logs from a Logstash agent

MongoDB metrics source

mongodb_metrics

Collect metrics from the MongoDB database

Read observability data from subjects on the NATS messaging system

NGINX metrics source

Collect metrics from NGINX

OpenTelemetry source

Receive OTLP data through gRPC or HTTP.

PostgreSQL metrics source

postgresql_metrics

Collect metrics from the PostgreSQL database

Prometheus Pushgateway source

prometheus_pushgateway

Collect metrics from Prometheus

Prometheus remote write source

prometheus_remote_write

Collect metrics from Prometheus

Prometheus scrape source

prometheus_scrape

Collect metrics via the Prometheus client

Collect observability events from Apache Pulsar topics

Collect observability data from Redis.

Collect logs using the socket client

Splunk HEC source

Receive logs from Splunk

Static metrics source

Publish statically configured metrics on an interval

Collect metrics emitted via StatsD protocol

Collect logs sent via stdin

Collect logs sent via Syslog

Collect observability data from another Vector instance

Transforms count 14

Remap with VRL transform

Modify your observability data as it passes through your topology using Vector Remap Language (VRL)

Aggregate transform

Aggregate metrics passing through a topology

AWS EC2 metadata transform

aws_ec2_metadata

Parse metadata emitted by AWS EC2 instances

Dedupe transform

Deduplicate logs passing through a topology

Exclusive Route transform

exclusive_route

Routes events from one or more streams to unique sub-streams based on a set of user-defined conditions.

Filter transform

Filter events based on a set of conditions

Log to metric transform

Convert log events to metric events

Modify event data using the Lua programming language

Metric to log transform

Convert metric events to log events

Reduce transform

Collapse multiple log events into a single event based on a set of conditions and merge strategies

Route transform

Split a stream of events into multiple sub-streams based on user-supplied conditions

Sample transform

Sample events from an event stream based on supplied criteria and at a configurable rate

Tag cardinality limit transform

tag_cardinality_limit

Limit the cardinality of tags on metrics events as a safeguard against cardinality explosion

Throttle transform

Rate limit logs passing through a topology

Sinks count 55

Send events to AMQP 0.9.1 compatible brokers like RabbitMQ

Deliver events to AppSignal

AWS Cloudwatch logs sink

aws_cloudwatch_logs

Publish log events to AWS Cloudwatch Logs

AWS Cloudwatch metrics sink

aws_cloudwatch_metrics

Publish metric events to AWS Cloudwatch Metrics

AWS Kinesis Data Firehose logs sink

aws_kinesis_firehose

Publish logs to AWS Kinesis Data Firehose topics

AWS Kinesis Streams logs sink

aws_kinesis_streams

Publish logs to AWS Kinesis Streams topics

Store observability events in the AWS S3 object storage system

Publish observability events to Simple Notification Service topics

Publish observability events to Simple Queue Service topics

Deliver log events to Axiom

Azure Blob Storage sink

Store your observability data in Azure Blob Storage

Azure Monitor Logs sink

azure_monitor_logs

Publish log events to the Azure Monitor Logs service

Send observability events nowhere, which can be useful for debugging purposes

ClickHouse sink

Deliver log data to the ClickHouse database

Display observability events in the console, which can be useful for debugging purposes

Deliver log data to the Databend database

Datadog events sink

Publish observability events to the Datadog Events API

Datadog logs sink

Publish log events to Datadog

Datadog metrics sink

datadog_metrics

Publish metric events to Datadog

Datadog traces sink

Publish traces to Datadog

Elasticsearch sink

Index observability events in Elasticsearch

Output observability events into files

GCP Chronicle Unstructured sink

gcp_chronicle_unstructured

Store unstructured log events in Google Chronicle

GCP Cloud Monitoring (formerly Stackdriver) sink

gcp_stackdriver_metrics

Deliver metrics to GCP’s Cloud Monitoring system

GCP Cloud Storage sink

gcp_cloud_storage

Store observability events in GCP Cloud Storage

GCP Stackdriver sink

gcp_stackdriver_logs

Deliver logs to GCP’s Cloud Operations suite

GCP PubSub sink

Publish observability events to GCP’s PubSub messaging system

GreptimeDB Logs sink

greptimedb_logs

Writes logs to GreptimeDB

GreptimeDB Metrics sink

greptimedb_metrics

Writes metrics to GreptimeDB

Deliver log events to Honeycomb

Deliver observability data to an HTTP server

Humio logs sink

Deliver log event data to Humio

Humio metrics sink

Deliver metric event data to Humio

InfluxDB logs sink

Deliver log event data to InfluxDB

InfluxDB metrics sink

influxdb_metrics

Deliver metric event data to InfluxDB

Publish observability data to Apache Kafka topics

Deliver log event data to the Loki aggregation system

Mezmo (formerly LogDNA) sink

Deliver log event data to Mezmo

Deliver observability event data to an MQTT broker

Publish observability data to subjects on the NATS messaging system

Deliver events to New Relic

Papertrail sink

Deliver log events to Papertrail from SolarWinds

Prometheus Exporter sink

prometheus_exporter

Output metric events to a Prometheus exporter running on the host

Prometheus remote write sink

prometheus_remote_write

Deliver metric data to a Prometheus remote write endpoint

Publish observability events to Apache Pulsar topics

Publish observability data to Redis.

Sematext logs sink

Publish log events to Sematext

Sematext metrics sink

sematext_metrics

Publish metric events to Sematext

Deliver logs to a remote socket endpoint

Splunk HEC logs sink

splunk_hec_logs

Deliver log data to Splunk’s HTTP Event Collector

Splunk HEC metrics sink

splunk_hec_metrics

Deliver metric data to Splunk’s HTTP Event Collector

Deliver metric data to a StatsD aggregator

Relay observability data to another Vector instance

Output observability events into WebHDFS

Deliver observability event data to a websocket listener