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

# Observability

> Monitor Midaz metrics, logs, and traces with OpenTelemetry, Client Collectors, and Lerian's managed Prometheus, Loki, Tempo, and Grafana observability stack.

Observability in **Midaz** lets you monitor metrics, logs, and traces across your deployed environments.

Midaz collects telemetry with the **OpenTelemetry framework**. A **Client Collector** in your infrastructure processes it. The collector then routes it securely to Lerian's managed stack: Prometheus, Loki, Tempo, and Grafana.

## How it works

***

Midaz uses a **dual observability model**:

* **Client side**: for local development, the collector configuration lives in `components/infra/grafana/otelcol-config.yaml`, mounted read-only into the bundled all-in-one Grafana/OTel container. It sets the collector's processors, filters, and exporters. For production and BYOC, configure the `otel-collector-lerian` subchart values instead.
* **Lerian side**: Lerian operates the managed collector and storage stack. Lerian keeps it secure and consistent.

<Note>
  The bundled collector config masks known sensitive keys (credentials, tokens, `legalDocument`, `accountAlias`) in log bodies and in the `app.request.payload` span attribute. Masking happens in the collector, so it applies after telemetry leaves the application process. The bundled local-development exporters run with TLS disabled (`insecure: true`). Enable TLS on the collector exporters for any non-local deployment.
</Note>

## Key benefits

***

* Unified view of metrics, logs, and traces in Grafana
* Built on OpenTelemetry standards
* Grafana preconfigured and operated by Lerian
* Secure routing and tenant isolation

<Tip>
  See [**Infra Tools → Observability**](/en/platform/observability) for advanced setup, collector configuration, and processor customization.
</Tip>