Attendance Operations
Summary
This section covers safe operation of Attendance Service, its dependencies, migrations, signals, outbox, Payroll lock integration, smoke/parity tooling, backfill, cutover, reconciliation, and escalation.
Audience
- DevOps/SRE, backend developers, support engineers, database/messaging owners, architects, and product owners
Overview
Attendance Service starts its web/API host, applies migrations unless operationally suppressed, optionally seeds only in development, exposes process health, emits structured telemetry, and runs an outbox relay. It depends conceptually on PostgreSQL, authentication metadata, tenant context, the shared broker, Payroll lock checks, and gateway routing.
Operational risks include shallow health coverage, eventual outbox/consumer consistency, transitional dual ownership, employee-profile synchronization gaps, application-only data invariants, and external Payroll availability.
Documentation map
- Operational overview
- Configuration reference
- Deployment and startup
- Health and observability
- Smoke testing
- Parity and cutover validation
- Backfill operations
- Data consistency and reconciliation
- Outbox operations
- Payroll dependency operations
- Cutover and rollback
- Support and escalation
- Operational checklist
Source References
microservices/src/attendance-service/Program.csmicroservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.csmicroservices/scripts/smoke-attendance.ps1microservices/docs/attendance-shift-cutover-runbook.md
Related Articles
See Also
Keywords
- Attendance operations
- Support
- Reliability
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly