Controls if the source will wait for destination sinks to deliver the events before acknowledging receipt.

acknowledgements

The address to accept connections on. The address _must_ include a port.

address

auth

password

username

A list of URL query parameters to include in the log event. These will override any values included in the body with conflicting names.

query_parameters

Configures the TLS options for incoming connections.

Absolute path to an additional CA certificate file, in DER or PEM format (X.509), or an in-line CA certificate in PEM format.

ca_file

Absolute path to a certificate file used to identify this server, in DER or PEM format (X.509) or PKCS#12, or an in-line certificate in PEM format. If this is set, and is not a PKCS#12 archive, `key_file` must also be set. This is required if `enabled` is set to `true`.

crt_file

Require TLS for incoming connections. If this is set, an identity certificate is also required.

enabled

Absolute path to a private key file used to identify this server, in DER or PEM format (PKCS#8), or an in-line private key in PEM format.

key_file

Pass phrase used to unlock the encrypted key file. This has no effect unless `key_file` is set.

key_pass

If `true`, Vector will require a TLS certificate from the connecting host and terminate the connection if the certificate is not valid. If `false` (the default), Vector will not request a certificate from the client.

verify_certificate

The component type. This is a required field for all components and tells Vector which component to use.

type

Receives log data from Heroku log drains via Heroku's logplex system.

Enriches data with useful Heroku context.

Syslog 6587

[Heroku](https://www.heroku.com) is a container-based platform for deploying and
managing applications. It's a platform as a service (PaaS) that is fully
managed, allowing developers on Heroku to focus on their applications
instead of their infrastructure.

Heroku

Setup a Heroku app by following the Heroku setup instructions.

Setup a Heroku app

By default, the `heroku_logs` source augments events with helpful
context keys.

context

Context

This component is stateless, meaning its behavior is consistent across each input.

state

State

Vector uses [OpenSSL](https://www.openssl.org/) for TLS protocols. You can
adjust TLS behavior via the `tls.*` options.

Transport Layer Security (TLS)

heroku_logs

An individual event from a batch of events received through an HTTP POST request.

The app name field extracted from log message.

app_name

The local hostname, equivalent to the `gethostname` command.

host

The message field, containing the plain text message.

message

The procid field extracted from log message.

proc_id

The exact time the event was ingested into Vector.

timestamp

line

The number of events accepted by this component either from tagged
origin like file and uri, or cumulatively from other origins.

events_in_total

The total number of events emitted by this component.

events_out_total

The number of bytes processed by the component.

processed_bytes_total

The total number of request read errors for this component.

request_read_errors_total

The total number of requests received by this component.

requests_received_total

A ratio from 0 to 1 of the load on a component. A value of 0 would indicate a completely idle component that is simply waiting for input. A value of 1 would indicate a that is never idle. This value is updated every 5 seconds.

Heroku Logplex

Configuration Options

Required Options

address(required)

type(required)

Advanced Options

acknowledgements(optional)

auth(optional)

tls(optional)

query_parameters(optional)

How it Works

State

Transport Layer Security (TLS)

Context