LMS Health and Diagnostics
Summary
Source-backed Draft reference for LMS Health and Diagnostics across the implemented Training Service and, where applicable, Gateway surface.
Audience
API consumers, engineering, QA, support, architecture, security, product, and implementation reviewers.
Reference Content
Confirmed routes and telemetry
| Capability | State |
|---|---|
| Process health route | Implemented with registered health checks |
| Training health-data route | Implemented; returns tenant-filtered entity counts and foundation state |
| Service information route | Implemented through shared envelope |
| Dependency readiness checks | Not implemented |
| Separate liveness/readiness routes | Not implemented |
| OpenTelemetry setup | Registered through shared observability extension |
| Correlation | Shared middleware executed |
| Exception recording | Shared observability plus local response mapping; exact exporter behavior is outside this API source |
| Custom metrics | Not found |
| Dashboard/alert integration | Not found |
The process health registration has no explicit Training database, Document Service, broker, or downstream probe in Program. It therefore must not be described as dependency readiness.
The health-data route reads tenant business counts and outbox count. It has no endpoint authorization declaration and may disclose operational/business state; public exposure requires confirmation. This documentation omits actual counts, environment details, and internal telemetry configuration.
Source References
microservices/src/training-service/Program.csmicroservices/src/training-service/Api/TrainingEndpoints.csmicroservices/src/shared-kernel/Extensions/ObservabilityExtensions.csmicroservices/src/shared-kernel/Middleware/CorrelationIdMiddleware.cs
Related Articles
See Also
Keywords
- LMS API
- Training Service
- Source-backed contract
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly