Tracer runs as a standalone service and is also bundled into the Midaz monorepo (
components/tracer) as part of the consolidation rollout. The variables below reflect the current, most complete shape, including the reservation gRPC seam the ledger calls into.Ports and health endpoints
See the health and readiness reference for the probe contract.Deployment and TLS
Application
Authentication and request handling
Database (PostgreSQL)
Tracer stores rules and usage counters in its owntracer database on the shared Midaz PostgreSQL primary.
Background workers
Readiness and draining
Reservation gRPC seam
Server side of the seam the Midaz ledger calls to reserve spending limits. Off unlessTRACER_GRPC_PORT is set.
Shared configuration backbone
The following blocks are identical across Lerian products and are documented in full in the BYOC configuration reference. They default off.- Access Manager authentication —
PLUGIN_AUTH_ENABLED,PLUGIN_AUTH_ADDRESS. Enable in production. - Multi-tenancy —
MULTI_TENANT_*, plus Tracer’s per-tenant pool knobs (MULTI_TENANT_MAX_TENANT_POOLS,MULTI_TENANT_MAX_OPEN_CONNS_PER_TENANT,MULTI_TENANT_TENANT_CAP_RETRY_AFTER_SECONDS). Off by default.APPLICATION_NAMEidentifies the module to Tenant Manager. - Event streaming —
STREAMING_*(lib-streaming producer). Off by default. - OpenTelemetry —
ENABLE_TELEMETRY,OTEL_*. Tracer also exposes a Prometheus/metricsendpoint.

