Skip to main content

Employee Health and Observability

Summary​

Employee Service exposes basic health, JSON console logging, correlation scopes, and OpenTelemetry tracing for inbound HTTP and outbound HTTP clients.

Audience​

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

Health semantics​

The mapped health endpoint confirms the registered health checks can report; only the base health-check registration is visible. No explicit database, broker, or downstream checks were added in Employee Service, so success must not be interpreted as dependency readiness.

Operational signal flow​

Confirmed signals​

Logs use UTC JSON console output and include scopes. Correlation middleware accepts or generates an identifier, attaches it to request/response and the log scope. OpenTelemetry identifies the service and instruments ASP.NET Core and HTTP clients; configured exporters are optional.

Gaps​

No dedicated readiness/liveness split, dependency health checks, Employee metrics, outbox backlog metric, consumer-lag signal, or alert thresholds were found. Relevant log categories include Employee handlers/infrastructure, shared correlation, messaging publisher, and startup migration warnings, but a production dashboard/runbook Requires confirmation.

Source References​

  • microservices/src/employee-service/Program.cs
  • microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
  • microservices/src/shared-kernel/Middleware/CorrelationIdMiddleware.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs

See Also​

Keywords​

  • health endpoint
  • OpenTelemetry
  • correlation ID

Revision Information​

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