Overview
These integrations collect logs, metrics, and, for some sources, request traces from self-hosted infrastructure and databases. Each page documents the signals the source actually exposes and the configuration used to send them to Bronto — an OpenTelemetry Collector pipeline for most sources, and the source’s own exporter settings where it speaks OTLP itself.These pages cover infrastructure and middleware you run yourself. To collect logs, metrics, and traces from your own application code, instrument it with the OpenTelemetry SDK.
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.Ingestion method
Most sources in this section are collected with the OpenTelemetry Collector. Docker Build and Keycloak are the exceptions — both are already instrumented with OpenTelemetry and export their traces to Bronto directly, with no Collector in between. Keycloak’s metrics are the usual Prometheus scrape. Log receivers tail files or container output, while metric receivers scrape the source’s monitoring endpoint or operating-system APIs. The Collector forwards only what it receives, so each integration page identifies the source-side feature that must be enabled. For Windows hosts, see Collecting Windows OS Logs and Metrics for Windows Event Log and IIS collection, plus Windows performance-counter, IIS, and SQL Server metrics.For assistance or questions, contact support@bronto.io.