Use the following single line command to configure the Vector repository and install the Vector log collector.
curl --proto '=https' --tlsv1.2 -sSfL https://sh.vector.dev | bash

​
Configure Vector

After installation, a Vector http sink must be configured to communicate with Bronto.
sources:
  app_logs:
    type: file
    include:
      - /path/to/your/logs
sinks:
  bronto:
    type: "http"
    inputs: ["app_logs"]
    uri: "https://ingestion.<REGION>.bronto.io:443/"
    compression: "gzip"
    encoding:
      codec: "json"
    framing:
      method: "newline_delimited"
    method: "post"
    request:
      headers:
        x-bronto-api-key:  <YOUR_API_KEY>
        x-bronto-dataset: <YOUR_DATASET_NAME>
        x-bronto-collection:  <YOUR_COLLECTION_NAME>
        x-bronto-tags: <key1=value1,key2=value2>
ParameterValueRequirementDescription
typeHTTPRequiredSpecifies the output sink used by Vector.
inputsapp_logsRequiredThe sources/transform ids to send to Bronto, wildcards (*) is also supported
urihttps://ingestion.<REGION>.bronto.io:443/RequiredThe Bronto endpoint responsible for ingesting log data. Regions supported are EU & US
encoding.codecjsonRequiredSpecifies the data format to be used in the HTTP request body.
framing.methodnewline_delimitedRequired (Since v0.23)Specifies the events are separated when encoding the HTTP request body.
methodpostRequiredSpecifies the method to use for the HTTP request.
compressgzipOptionalRecommended. Compresses the payload in GZIP format. Bronto supports and recommends using gzip for efficient data transmission.
header (x-bronto-api-key)Your API KeyRequiredYour Bronto API key.
header (x-bronto-dataset)Your Dataset or Service NameRequiredSpecifies the name of the service.
header (x-bronto-collection)Your Collection or Service NamespaceOptionalSpecifies the namespace for organizational purposes.
tags (x-bronto-tags)TagsOptionalSpecifies the tags to apply to logs. A tag is a key-value pair applied to a log to hold metadata about that log. Each tag is a label consisting of a key and a required value.
The table below lists the parameters used to determine the Bronto dataset associated with the ingested data, ordered from highest to lowest precedence.
Parameter NameParameter Type
x-bronto-datasetHTTP Header
x-bronto-log-nameHTTP Header
kubernetes.pod_annotations.logs.bronto.io/datasetLog Metadata
service.nameLog Metadata
service_nameLog Metadata
kubernetes.pod_labels.app.kubernetes.io/nameLog Metadata
The table below lists the parameters used to determine the Bronto collection associated with the ingested data, ordered from highest to lowest precedence.
Parameter NameParameter Type
x-bronto-collectionHTTP Header
x-bronto-logsetHTTP Header
kubernetes.pod_annotations.logs.bronto.io/collectionLog Metadata
service.namespaceLog Metadata
service_namespaceLog Metadata
Finally the table below lists the parameters used to assign tags to datasets, ordered from highest to lowest precedence.
Parameter NameParameter TypeExample
x-bronto-tagsHTTP Headerx-bronto-tags: tag1=value1,tag2=value2,…
kubernetes.pod_annotations.tags.logs.bronto.io/<TAG_NAME>Log Metadatakubernetes.pod_annotations.tags.logs.bronto.io/tag1: value1

​
Verify Log Collection

Once you have applied your configuration and restarted Vector, you can expect to see your log data being ingested to Bronto and accessible via the Search page.