Skip to main content
The Midaz chart includes an optional observability stack based on Grafana OTEL LGTM — a pre-configured bundle that provides Loki for log aggregation, Grafana for dashboards, Tempo for distributed traces, and Mimir for metrics. When enabled (grafana.enabled: true), this stack deploys alongside Midaz and automatically collects telemetry from all services.

​
Accessing the Grafana dashboard

You can access the Grafana dashboard using one of two options:

​
Local access

To access the dashboard locally run: 
kubectl port-forward svc/midaz-grafana 3000:3000 -n midaz
Then use http://localhost:3000 to open the dashboard.

​
Ingress access

To expose Grafana within your cluster or private network via DNS, enable and configure Ingress like this: 
grafana:
  enabled: true
  name: grafana
  ingress:
    enabled: true
    className: "nginx"
    annotations:
      nginx.ingress.kubernetes.io/rewrite-target: /
    hosts:
      - host: "midaz-otel.example.com"
        paths:
          - path: /
            pathType: Prefix
    tls: []

​
Disabling observability

You can disable the observability stack entirely by setting: 
grafana:
  enabled: false

​
Default dashboards

The default installation provides the Grafana UI with access to Loki, Tempo, and Mimir data sources. No pre-built dashboards are included — you can import Lerian’s recommended dashboards or create your own based on the available telemetry data.

​
Connecting external OTEL collectors

For production deployments, use the otel-collector-lerian chart to route telemetry to your existing observability infrastructure (Datadog, New Relic, Elastic, etc.). This chart is disabled by default. To enable it: 
otel-collector-lerian:
  enabled: true
For full configuration options, see Infrastructure Helm charts.