The sources/transform ids to send to Bronto, wildcards (*) is also supported
uri
https://ingestion.<REGION>.bronto.io:443/
Required
The Bronto endpoint responsible for ingesting log data. Regions supported are EU & US
encoding.codec
json
Required
Specifies the data format to be used in the HTTP request body.
framing.method
newline_delimited
Required (Since v0.23)
Specifies the events are separated when encoding the HTTP request body.
method
post
Required
Specifies the method to use for the HTTP request.
compress
gzip
Optional
Recommended. Compresses the payload in GZIP format. Bronto supports and recommends using gzip for efficient data transmission.
header (x-bronto-api-key)
Your API Key
Required
Your Bronto API key.
header (x-bronto-dataset)
Your Dataset or Service Name
Required
Specifies the name of the service.
header (x-bronto-collection)
Your Collection or Service Namespace
Optional
Specifies the namespace for organizational purposes.
tags (x-bronto-tags)
Tags
Optional
Specifies 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 Name
Parameter Type
x-bronto-dataset
HTTP Header
x-bronto-log-name
HTTP Header
kubernetes.pod_annotations.logs.bronto.io/dataset
Log Metadata
service.name
Log Metadata
service_name
Log Metadata
kubernetes.pod_labels.app.kubernetes.io/name
Log Metadata
The table below lists the parameters used to determine the Bronto collection associated with the ingested data, ordered
from highest to lowest precedence.
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.