Attendance Health and Observability

Summary

Attendance exposes process health and shared observability, but dependency readiness and dedicated business metrics are not confirmed.

Audience

• DevOps/SRE, support engineers, developers, and architects

Signal flow

Process health does not prove database, broker, Payroll, authentication metadata, or gateway readiness. No dedicated liveness/readiness split or dependency probe is confirmed. Correlation middleware, shared OpenTelemetry registration, and structured logs provide request traces; business audit/timeline provide operation history but are not universal change capture.

Monitor process restarts, request failure categories, latency/traces, migration errors, Payroll-call failures, relay iteration failures, and pending/failed outbox growth. Attendance-specific metrics, alert thresholds and dashboard ownership are Requires confirmation.

Source References

• microservices/src/attendance-service/Program.cs
• microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
• microservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.cs
• microservices/src/attendance-service/Infrastructure/PayrollLockClient.cs

Related Articles

• Attendance operations
• Attendance troubleshooting
• Attendance technical documentation

See Also

• Attendance database documentation
• Attendance events documentation

Keywords

• Attendance operations
• Support
• Reliability

Revision Information

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