Leave Observability

Summary

Shared Kernel provides structured logging, correlation, ASP.NET Core/HTTP tracing, and OpenTelemetry export hooks; Leave adds audit/timeline and background-service logs.

Audience

Developers, DevOps/SRE, architects, QA, and support.

Overview

The service records JSON structured logs with scopes, request correlation, server spans, and external HTTP spans. Application operations produce audit/timeline evidence. Outbox status and consumer logs expose publication/projection progress conceptually.

No dedicated Leave business metrics, cache metrics, dependency dashboards, or consumer-lag instrumentation were found. Outbox publication does not prove consumer completion. Dependency failures are logged by clients/hosted services, subject to safe-data practices.

Source References

• microservices/src/leave-service/Program.cs
• microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
• microservices/src/shared-kernel/Middleware/CorrelationIdMiddleware.cs
• microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
• microservices/src/leave-service/Messaging/OutboxRelayHostedService.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Observability
• Technical architecture

Revision Information

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