Skip to main content

Employee Health Checks

Summary​

Employee Service registers ASP.NET Core health services and maps a single /health endpoint. No Employee dependency checks or separate liveness/readiness endpoints are registered.

Audience​

  • Backend developers and QA engineers
  • DevOps engineers and solution architects

Reference Content​

Current behavior​

  • AddHealthChecks is registered in the composition root.
  • /health maps the default health-check pipeline.
  • A shared service-information endpoint is also mapped, but it is informational rather than a dependency health check.
  • Platform Service has service-health probing capability and includes Employee in the broader service registry landscape; environment activation Requires confirmation.

Liveness and readiness​

The single endpoint has no source-confirmed tag or predicate separating liveness from readiness. It reports host health based on registered checks. Because no persistence, broker, downstream, or outbox check is registered, it does not prove those dependencies are available.

Dependency health​

Not implemented in reviewed Employee source:

  • Persistence connectivity check.
  • Message-broker connectivity check.
  • Outbox backlog/relay check.
  • Gateway or Identity dependency check.
  • Separate startup, liveness, or readiness policy.

Operational probe configuration and production thresholds Require confirmation.

Source References​

  • microservices/src/employee-service/Program.cs
  • microservices/src/shared-kernel/Extensions/EndpointRouteBuilderExtensions.cs
  • microservices/src/platform-service/Workers/ServiceHealthMonitor.cs

See Also​

Keywords​

  • Service health
  • Readiness gap
  • Dependency probe

Revision Information​

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