Skip to main content

Overview

These integrations collect logs — and, for some sources, request traces — from self-hosted infrastructure and databases and send them to Bronto with the OpenTelemetry Collector. Each page covers where the source writes its logs, the receiver configuration to collect them, and the Bronto exporter setup.
These pages cover infrastructure and middleware you run yourself. To collect logs and traces from your own application code, instrument it with the OpenTelemetry SDK. For managed cloud services, see the AWS and Azure ingestion overviews.

Supported sources

Each source below links to a per-integration page with the exact receiver configuration and where that technology writes its logs. All of them are collected with the OpenTelemetry Collector.
SourceTypeCollected
KubernetesContainer platformPod logs via a Collector DaemonSet
DockerContainer platformContainer logs (Docker and Docker Compose)
NGINXWeb server / proxyAccess and error logs, plus request traces
HAProxyLoad balancer / proxyAccess logs
TraefikReverse proxyAccess logs
EnvoyProxyAccess logs
IstioService meshService-mesh access logs
KafkaMessage brokerBroker logs
RabbitMQMessage brokerBroker logs
PostgreSQLDatabaseServer logs
MySQLDatabaseError and slow query logs
MongoDBDatabaseServer logs
RedisDatabase / cacheServer logs

Ingestion method

Every source in this section is collected with the OpenTelemetry Collector, which tails the source’s log files (or reads its container output) and forwards logs and traces to Bronto over OTLP/HTTP. The Collector forwards only what it receives, so each integration page shows the receiver you add to pick up that source. See Getting your data into the Collector for how application, infrastructure, and platform log sources fit together. For Windows hosts, see Collecting Windows OS Logs for Windows Event Log and IIS collection.
For assistance or questions, contact support@bronto.io.