Attendance Operational Overview
Summary
Attendance Service owns Attendance/Time Office runtime processing while gateway and monolith compatibility remain Transitional.
Audience
- DevOps/SRE, service owners, support engineers, architects, and QA engineers
Overview
Runtime responsibilities include Attendance commands/queries, Time Office configuration, tenant-scoped persistence, migrations, audit/timeline history, transactional outbox publication, and Payroll lock checks. Dependencies are PostgreSQL, authentication/signing metadata, tenant-bearing requests, shared messaging, Payroll availability for lock-sensitive operations, and gateway reachability for client traffic.
Startup registers persistence, messaging, authorization placeholders, observability, health, API discovery, the Payroll client, and the outbox relay. Current health is process-level and does not prove dependencies. Structured logging, correlation middleware and OpenTelemetry registration exist; dedicated Attendance business metrics and readiness probes are gaps.
Use smoke, parity, backfill validation, and cutover go/no-go tooling only in approved isolated environments. Support ownership spans Attendance, Time Office/product, Gateway, Payroll, database, messaging, identity/security, and DevOps.
Source References
microservices/src/attendance-service/Program.csmicroservices/src/attendance-service/Infrastructure/AttendanceDbContext.csmicroservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.csmicroservices/src/attendance-service/Infrastructure/PayrollLockClient.cs
Related Articles
See Also
Keywords
- Attendance operations
- Support
- Reliability
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly