For detailed installation instructions check out the OpenTelemetry documentation site.

​
Configure OpenTelemetry

Copy the below configuration to your open telemetry configuration file. On most linux distributions, this is located at /etc/otel/config.yaml.
receivers:
  filelog/<DATASET_NAME>:
    include:
      - /path/to/your/logs
    resource:
      service.name: <YOUR_DATASET_NAME>
      service.namespace: <YOUR_COLLECTION_NAME>

processors:
  batch:

exporters:
  otlphttp/bronto:
    logs_endpoint: "https://ingestion.<REGION>.bronto.io/v1/logs"
    compression: none
    headers:
      x-bronto-api-key: <YOUR_API_KEY>

service:
  pipelines:
    logs:
      receivers: [filelog/<DATASET_NAME>]
      processors: [batch]
      exporters: [otlphttp/bronto]
  # Useful for debugging    
  # telemetry:
    # logs:
      # level: "debug"
      # output_paths: [/path/to/debug.log]
The following tables outline the order of precedence for the headers and attributes used to resolve service names and namespaces. For service names:
Parameter NameParameter Type
x-bronto-datasetHTTP Header
x-bronto-service-nameHTTP Header
x-bronto-log-nameHTTP Header
logs.bronto.io/datasetLog Metadata
service.nameLog Metadata
lognameLog Metadata
And for service namespaces:
Parameter NameParameter Type
x-bronto-collectionHTTP Header
x-bronto-service-namespaceHTTP Header
x-bronto-logsetHTTP Header
logs.bronto.io/collectionLog 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,…
tags.logs.bronto.io/<TAG_NAME>Log Metadatatags.logs.bronto.io/tag1: value1

​
Verify Log Collection

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