Skip to main content

Attendance Health Checks

Summary​

The current health surface reports process-level ASP.NET Core health registration only.

Audience​

DevOps and support engineers, backend developers, architects, and QA engineers.

Reference Content​

The composition root registers the standard health-check framework and maps a health endpoint. No Attendance-specific database, event-broker, Payroll dependency, outbox-lag, migration, or employee-profile freshness health check is registered. There is no separate readiness and liveness configuration in the service source.

A healthy response therefore confirms that the process can serve the health pipeline; it does not prove persistence connectivity, broker delivery, Payroll lock availability, migration currency, or full business readiness. Broker publication is retried in the background and Payroll lock failures are handled by the client independently of health.

Deployment platforms must not infer dependency readiness from the current process check. Detailed probe configuration and operational response belong in the future Operations documentation. Dependency checks, readiness/liveness separation, and degraded-state semantics are Not implemented / Requires confirmation.

Source References​

  • microservices/src/attendance-service/Program.cs
  • microservices/src/attendance-service/Infrastructure/PayrollLockClient.cs
  • microservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.cs

See Also​

Keywords​

  • Attendance Service
  • Attendance Health Checks

Revision Information​

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