Skip to main content
The Midaz chart does not deploy an observability stack. It emits OpenTelemetry traces and metrics and expects you to run the collector and the backend. The chart only controls whether it injects the OTEL environment variables into the ledger, crm, and tracer deployments.
The chart contains no Grafana templates. The grafana: key still exists in values.yaml, but it renders nothing, so setting grafana.enabled: true has no effect.

​
Injecting the OTEL environment variables

The otel-collector-lerian.enabled key controls injection and defaults to true:
The schema for this key is strict. The schema accepts only enabled. It rejects legacy keys (external, extraEnvs, exporters, opentelemetry-collector) at helm install/helm upgrade time.
When enabled, the chart adds these variables to the ledger, crm, and tracer containers:

​
What you must provide

The endpoint is fixed at $(HOST_IP):4317, the node the pod runs on. Keeping enabled: true therefore needs an OTLP collector on port 4317 on every node, usually a DaemonSet with hostNetwork or a host port. Without one, the applications export to a dead endpoint.

​
Using a different endpoint

You can send telemetry somewhere else: a central collector Service, a managed backend, or your existing observability infrastructure. Leave injection off and set the endpoint directly in the application ConfigMap:

​
Dashboards

No dashboards ship with the chart. Build them in whatever backend receives the telemetry. For the standalone collector chart, see Infrastructure Helm charts.