Leave Health and Observability

Summary

Leave exposes process health and shared structured logging/tracing, while dependency readiness, business metrics, consumer lag, and backlog metrics remain gaps.

Audience

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

Overview

The health endpoint reports process-level health only. No explicit database, broker, Attendance, Workflow, consumer, or outbox probes and no separate readiness/liveness endpoints were found.

Shared observability supplies structured logs, correlation identifiers, server tracing, external HTTP tracing, and optional OpenTelemetry export. Audit/timeline records and outbox states provide domain/delivery evidence. Avoid logging reasons or personal Leave data during investigation.

Dedicated Leave metrics, dependency dashboards, consumer-lag measures, and terminal outbox alerting are Not implemented / Requires confirmation.

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

• Leave Operations
• Leave technical documentation

See Also

• Leave events
• Leave troubleshooting

Keywords

• Leave operations
• Leave Health and Observability
• Service support

Revision Information

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