Ingesting Infrastructure Telemetry into Bronto

An overview of self-hosted infrastructure and database integrations that send logs, metrics, and traces to Bronto.

​

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 configuration and where that technology writes its telemetry.

Source	Type	Collected
Kubernetes	Container platform	Pod logs, kubelet metrics, and application telemetry
Docker	Container platform	Container logs and runtime metrics
Docker Build	Build system	BuildKit build traces (per-step durations and cache hits)
Host metrics	Operating system	CPU, memory, disk, filesystem, network, paging, and process metrics
NGINX	Web server / proxy	Access and error logs, server metrics, and request traces
HAProxy	Load balancer / proxy	Access logs and Prometheus metrics
Traefik	Reverse proxy	Access logs and Prometheus metrics
Envoy	Proxy	Access logs, Prometheus metrics, and request traces
Istio	Service mesh	Mesh access logs, Envoy metrics, and traces
Keycloak	Identity provider	Login, token, and JDBC traces, trace-correlated server logs, and Prometheus metrics
Kong Gateway	API / AI gateway	Request traces, access and runtime logs, gateway metrics, and AI token usage
Kafka	Message broker	Broker logs and cluster/consumer metrics
RabbitMQ	Message broker	Broker logs and queue metrics
PostgreSQL	Database	Server logs and database metrics
MySQL	Database	Error/slow-query logs and database metrics
MongoDB	Database	Server logs and database metrics
Redis	Database / cache	Server logs and cache metrics

---

​

Ingestion method

Most sources in this section are collected with the OpenTelemetry Collector. Docker Build, Keycloak and Kong Gateway are the exceptions — all three are already instrumented with OpenTelemetry and export 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 [e-mail].