Skip to main content
Vector forwards logs to Bronto using its built-in HTTP sink. This page covers Vector configuration only. For installation instructions, see the Vector installation guide.

​
Endpoint and authentication

Use the ingestion endpoint for your Bronto region:
RegionHost
EUhttps://ingestion.eu.bronto.io:443
UShttps://ingestion.us.bronto.io:443
Every request requires these headers:
HeaderRequiredDescription
x-bronto-api-keyRequiredYour Bronto API key.
x-bronto-datasetRequiredThe dataset to route logs to.
x-bronto-collectionRequiredThe collection to group datasets under.
x-bronto-tagsOptionalKey-value tag pairs (e.g. env=prod,team=platform). See Partitions.

​
Minimal configuration

Tail a log file and forward to Bronto.
/etc/vector/vector.yaml
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>
For the full HTTP sink configuration reference, see the Vector HTTP sink documentation.

​
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.