LMS Logging and Observability

Summary

Shared observability configures structured JSON console logging, service resource identity, ASP.NET Core tracing, HTTP-client tracing, exception recording, and optional configured trace exporters. Correlation middleware is enabled. Training exposes a framework health check and tenant-scoped health-data read.

No Training-specific metrics instrumentation, business counters, dependency health probes, readiness/liveness distinction, dashboard, alert, service objective, or Training hosted-service logging exists. Shared outbox processor logging applies only if invoked. Operational identifiers and exporter settings are excluded.

Requires confirmation

Fine-grained authorization, production ownership, operational governance, and future architectural boundaries require confirmation where not implemented.

Source References

• microservices/src/training-service/Program.cs
• microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
• microservices/src/training-service/Application/DocumentServiceClient.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs

Related Articles

• LMS technical documentation
• LMS business documentation

See Also

• Technical limitations
• Technical source map

Keywords

• LMS technical architecture
• Source-backed implementation

Revision Information

• Status: Draft
• Last reviewed: 2026-07-17
• Review cycle: Quarterly