LMS Operations Documentation

Summary

Training registers persistence, tenant context, shared messaging, observability, health, and a Document HTTP client. Operational maturity is Transitional because publication triggering, production runbooks, alerting, rollback, and ownership are incomplete.

Audience

Engineering, QA, support, operations, architecture, security, and implementation teams.

Overview

Operations documentation provides safe evidence categories only. It is not a production runbook.

Documentation map

• Runtime overview, startup, and configuration reference
• Health and observability, outbox, and document operations
• Notification and Gateway dependencies
• Smoke testing, rollback, escalation, and operational checklist

Requires confirmation

Production deployment ownership, health semantics, service objectives, alerting, relay ownership, recovery approvals, retention, and escalation contacts require confirmation.

Source References

• microservices/src/training-service/Program.cs
• microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
• microservices/src/shared-kernel/Extensions/ServiceCollectionExtensions.cs
• microservices/src/training-service/Infrastructure/Persistence.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
• microservices/scripts/smoke-training.ps1

Related Articles

• LMS module
• Technical documentation
• Troubleshooting

See Also

• Event limitations
• Reference limitations

Keywords

• LMS operations
• Training runtime

Revision Information

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