For detailed installation instructions check out the OpenTelemetry documentation site.
Ubuntu/Debian Redhat/CentOS Docker MacOS Kubernetes Copy the below configuration to your open telemetry configuration file. On most linux distributions, this is located at /etc/otel/config.yaml.
receivers : filelog/ < SERVICE_NAMESPACE > :
include :
- / path/ to/ your/ logs
resource :
service. name : < YOUR_SERVICE_NAME >
service. namespace : < YOUR_SERVICE_NAMESPACE >
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/ < LOGSET_LOG > ]
processors : [ batch]
exporters : [ otlphttp/ bronto]
# Useful for debugging
# telemetry:
# logs:
# level: "debug"
# output_paths: [ / path/ to/ debug. log ]
Copy the below configuration to your open telemetry configuration file. On most linux distributions, this is located at /etc/otel/config.yaml.
receivers : filelog/ < SERVICE_NAMESPACE > :
include :
- / path/ to/ your/ logs
resource :
service. name : < YOUR_SERVICE_NAME >
service. namespace : < YOUR_SERVICE_NAMESPACE >
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/ < LOGSET_LOG > ]
processors : [ batch]
exporters : [ otlphttp/ bronto]
# Useful for debugging
# telemetry:
# logs:
# level: "debug"
# output_paths: [ / path/ to/ debug. log ]
Copy the below configuration to your open telemetry configuration file. On most linux distributions, this is located at /etc/otel/config.yaml.
receivers : filelog/ < SERVICE_NAMESPACE > :
include :
- / path/ to/ your/ logs
resource :
service. name : < YOUR_SERVICE_NAME >
service. namespace : < YOUR_SERVICE_NAMESPACE >
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/ < LOGSET_LOG > ]
processors : [ batch]
exporters : [ otlphttp/ bronto]
# Useful for debugging
# telemetry:
# logs:
# level: "debug"
# output_paths: [ / path/ to/ debug. log ]
Copy the below configuration to your open telemetry configuration file. On most linux distributions, this is located at /etc/otel/config.yaml.
receivers : filelog/ < SERVICE_NAMESPACE > :
include :
- / path/ to/ your/ logs
resource :
service. name : < YOUR_SERVICE_NAME >
service. namespace : < YOUR_SERVICE_NAMESPACE >
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/ < LOGSET_LOG > ]
processors : [ batch]
exporters : [ otlphttp/ bronto]
# Useful for debugging
# telemetry:
# logs:
# level: "debug"
# output_paths: [ / path/ to/ debug. log ]
Copy the below configuration to your open telemetry configuration file. On most linux distributions, this is located at /etc/otel/config.yaml.
receivers : filelog/ < SERVICE_NAMESPACE > :
include :
- / path/ to/ your/ logs
resource :
service. name : < YOUR_SERVICE_NAME >
service. namespace : < YOUR_SERVICE_NAMESPACE >
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/ < LOGSET_LOG > ]
processors : [ batch]
exporters : [ otlphttp/ bronto]
# Useful for debugging
# telemetry:
# logs:
# level: "debug"
# output_paths: [ / path/ to/ debug. log ]
Following the official documentation on defining OTEL exporters , a Bronto exporter for Kubernetes can be configured the following way:
exporters:
otlphttp/bronto:
logs_endpoint: "https://ingestion.<REGION>.bronto.io/v1/logs"
compression: none
headers:
x-bronto-api-key: <YOUR_API_KEY>
x-bronto-service-namespace: <SERVICE_NAMESPACE>
where the x-bronto-service-namespace header should identify the Kubernetes cluster where the data originates (e.g., cluster1-prod-us-east-1). Service names are inferred by Bronto based on log attributes.
The following tables outline the order of precedence for the headers and attributes used to resolve service names and namespaces. For service names:
Parameter Name Parameter Type x-bronto-service-name HTTP Header x-bronto-log-name HTTP Header logs.bronto.io/dataset Log Metadata service.name Log Metadata logname Log Metadata
And for service namespaces:
Parameter Name Parameter Type x-bronto-service-namespace HTTP Header x-bronto-logset HTTP Header logs.bronto.io/collection Log Metadata service.namespace Log Metadata
Finally the table below lists the parameters used to assign tags to datasets, ordered from highest to lowest precedence.
Parameter Name Parameter Type Example x-bronto-tags HTTP Header x-bronto-tags: tag1=value1,tag2=value2,… tags.logs.bronto.io/<TAG_NAME> Log Metadata tags.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.
