Ports and health endpoints
See the health and readiness reference for the probe contract.Deployment and TLS
Application
Rule evaluation
Authentication and request handling
RI permission declaration
Database (PostgreSQL)
Tracer stores rules and usage counters in its owntracer database on the shared Midaz PostgreSQL primary. A dedicated migration-runner image applies the schema migration before the application starts. The service boots against an already-migrated schema and does not run migrations in-process.
Background workers
Reservations
Readiness and draining
Reservation gRPC seam
Server side of the seam the Midaz ledger calls to reserve spending limits. Off unless you setTRACER_GRPC_PORT.
Shared configuration backbone
The following blocks are identical across Lerian products. The BYOC configuration reference documents them in full. They default off.- Access Manager authentication:
PLUGIN_AUTH_ENABLED,PLUGIN_AUTH_ADDRESS. Enable in production. In discovery-enabled builds (see Service discovery below), Tracer resolves the Access Manager host through Consul. It falls back toPLUGIN_AUTH_ADDRESSif resolution fails. Current builds always usePLUGIN_AUTH_ADDRESS. - Multi-tenancy:
MULTI_TENANT_*, plus Tracer’s per-tenant pool knobs (MULTI_TENANT_MAX_TENANT_POOLS,MULTI_TENANT_MAX_OPEN_CONNS_PER_TENANT,TENANT_CAP_RETRY_AFTER_SECONDS). Off by default.APPLICATION_NAMEidentifies the module to Tenant Manager. - Service discovery:
SD_*(Consul). Off by default. WhenSD_ENABLED=true, Tracer registers itself asmidaz-tracer(advertising the HTTP port fromSERVER_ADDRESS, default4020) and resolves Access Manager through Consul. If that resolution fails, it falls back to the staticPLUGIN_AUTH_ADDRESS. Discovery requiresSD_EXTERNAL_ADDRESSorSD_INTERNAL_ADDRESS. Tracer is the server on the reservation gRPC seam and does not advertise it. - Event streaming:
STREAMING_*(lib-streaming producer). Off by default. - OpenTelemetry:
ENABLE_TELEMETRY,OTEL_*. Tracer also exposes a Prometheus/metricsendpoint.

