LMS Health and Observability
Summary
The service exposes a health endpoint, service-information response, JSON console logging, request/HTTP tracing, correlation middleware, audit rows, timeline rows, and outbox diagnostics.
Reference Content
| Signal | Evidence | Limitation |
|---|---|---|
| Health | Health services and mapped health route | Dependency depth and readiness semantics not defined |
| Logging | Structured JSON console provider | Alert routing and retention not found |
| Tracing | Server and HTTP-client instrumentation | Export depends on configuration; objectives absent |
| Correlation | Shared correlation middleware | Training event producers leave event correlation unset |
| Business evidence | Audit and timeline storage | Not a substitute for operational monitoring |
| Outbox diagnostics | Read surface exposes processing categories | Relay liveness cannot be inferred |
Collect sanitized correlation, time window, operation category, status category, and dependency category only.
Safety and confirmation boundary
No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.
Source References
microservices/src/training-service/Program.csmicroservices/src/shared-kernel/Extensions/ObservabilityExtensions.csmicroservices/src/shared-kernel/Extensions/ServiceCollectionExtensions.csmicroservices/src/training-service/Api/TrainingEndpoints.cs
Related Articles
See Also
Keywords
- LMS operations
- LMS Health and Observability
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly