Logging and Observability
Audience
Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.
Reference Content
This page records source-verified technical behavior and boundaries for the workforce-scheduling capability.
Summary
The service uses structured JSON logs, request correlation scopes, distributed tracing for inbound web requests and outbound HTTP calls, health reporting, and service-information metadata. Trace export is configurable.
Scheduling evidence
Shift-policy commands write tenant-scoped audit and timeline records. Query services expose filtered diagnostics. Audit captures actor and serialized details; timeline records a human-oriented description and metadata. These records are persisted separately from ordinary logs.
Gaps
No scheduling-specific metrics, counters, latency histograms, traces around policy resolution, overlap-conflict telemetry, alert definitions, service objectives, dashboards, or runbook ownership were found. Command services do not use dedicated structured log events. Scheduling changes do not map to the outbox, so downstream observability cannot rely on change events.
Operational caution
Correlation values may be accepted from the incoming request. Trust-boundary normalization and log-forgery controls were not verified. Audit/timeline retention and access-control policy also require confirmation.
Source References
microservices/src/shared-kernel/Extensions/ObservabilityExtensions.csmicroservices/src/shared-kernel/Middleware/CorrelationIdMiddleware.csmicroservices/src/attendance-service/Infrastructure/AttendanceDbContext.csmicroservices/src/attendance-service/Program.cs
Related Articles
See Also
Keywords
- Workforce scheduling
- Shift policy
- Attendance integration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20