tenant-aware-logging

To attach tenant_id to logs, instrument HTTP middleware to inject the tenant context into the request context. A Logger helper then extracts this context to enrich all log entries across HTTP handlers, background workers, and asynchronous tasks.

Propagating tenant context across microservices requires passing a shared tenant_id key through context boundaries. This enables consistent per-tenant log filtering and traceability across distributed SaaS stack components.

Yes, per-tenant log filtering works in Loki, Datadog, and CloudWatch. By injecting tenant_id into every log entry, you can query and isolate specific tenant activity across your observability platforms.

Yes, shared context keys are required for tenant-aware logging. A standardized tenant_id key allows middleware and Logger helpers to consistently inject, propagate, and reconstruct tenant context across all services.

Tenant context gets lost in asynchronous tasks when it is not explicitly propagated. Reconstructing tenant context in background workers requires injecting the tenant_id into the job payload and re-establishing it in the worker's logging context.