> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bronto.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Ingesting Infrastructure Telemetry into Bronto

> An overview of self-hosted infrastructure and database integrations that send logs, metrics, and traces to Bronto with the OpenTelemetry Collector.

## 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 OpenTelemetry Collector configuration used to send them to Bronto.

<Note>
  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](/opentelemetry/overview).
</Note>

***

## 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.

| Source                         | Type                  | Collected                                                           |
| ------------------------------ | --------------------- | ------------------------------------------------------------------- |
| [Kubernetes](./kubernetes)     | Container platform    | Pod logs, kubelet metrics, and application telemetry                |
| [Docker](./docker)             | Container platform    | Container logs and runtime metrics                                  |
| [Docker Build](./docker-build) | Build system          | BuildKit build traces (per-step durations and cache hits)           |
| [Host metrics](./host-metrics) | Operating system      | CPU, memory, disk, filesystem, network, paging, and process metrics |
| [NGINX](./nginx)               | Web server / proxy    | Access and error logs, server metrics, and request traces           |
| [HAProxy](./haproxy)           | Load balancer / proxy | Access logs and Prometheus metrics                                  |
| [Traefik](./traefik)           | Reverse proxy         | Access logs and Prometheus metrics                                  |
| [Envoy](./envoy)               | Proxy                 | Access logs, Prometheus metrics, and request traces                 |
| [Istio](./istio)               | Service mesh          | Mesh access logs, Envoy metrics, and traces                         |
| [Kafka](./kafka)               | Message broker        | Broker logs and cluster/consumer metrics                            |
| [RabbitMQ](./rabbitmq)         | Message broker        | Broker logs and queue metrics                                       |
| [PostgreSQL](./postgresql)     | Database              | Server logs and database metrics                                    |
| [MySQL](./mysql)               | Database              | Error/slow-query logs and database metrics                          |
| [MongoDB](./mongodb)           | Database              | Server logs and database metrics                                    |
| [Redis](./redis)               | Database / cache      | Server logs and cache metrics                                       |

***

## Ingestion method

Almost every source in this section is collected with the [OpenTelemetry Collector](/agent-setup/open-telemetry) — [Docker Build](./docker-build) is the exception, as BuildKit exports its build traces to Bronto directly. 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](./azure-windows-logs) for Windows Event Log and IIS collection.

***

For assistance or questions, contact [support@bronto.io](mailto:support@bronto.io).