Skip to main content

Attendance Observability

Summary​

Attendance uses shared structured logging, correlation, OpenTelemetry tracing, audit/timeline records, and outbox status for complementary visibility.

Audience​

Developers, DevOps and support engineers, architects, and QA engineers.

Observability flow​

Shared observability clears default logging providers and emits structured JSON console logs with scopes. OpenTelemetry instruments inbound ASP.NET Core and outbound HTTP activity and can export traces through configured providers. Correlation middleware normalizes a correlation identifier across request, response, and log scope. The outbox processor and Payroll client log dependency failures; audit and timeline entries capture supported business changes.

No application metrics, custom Attendance spans, dashboards, alert rules, distributed-log backend, or confirmed outbox-lag metric are registered in the service. The cutover tooling can inspect outbox lag operationally, but that is not equivalent to continuous metrics. Sensitive attendance content should not be logged.

Source References​

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

See Also​

Keywords​

  • Attendance Service
  • Attendance Observability

Revision Information​

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