Helpdesk Logging and Observability

Audience

Developers, DevOps, support, security and architects.

Summary

Startup enables shared HR Suit observability and correlation handling, exposes health and service-information endpoints, and relies on framework logging plus domain audit/timeline records.

Reference Content

Structured logs are explicit for backfill start/failure and Document Service transport failure. Endpoint handlers do not contain broad business-operation logger calls; instead they persist ticket audit and timeline records. The outbox retains processing status, retry count and error text.

Shared observability implementation is external to the Helpdesk project, so exact exporters, sampling and production telemetry cannot be inferred from registration alone.

Requires confirmation

Telemetry exporters, dashboards, alerting, log retention/redaction, health dependency depth and support runbooks require confirmation.

Source References

• microservices/src/helpdesk-service/Program.cs
• microservices/src/helpdesk-service/Backfill/HelpdeskBackfill.cs
• microservices/src/helpdesk-service/Infrastructure/DocumentServiceClient.cs
• microservices/src/helpdesk-service/Infrastructure/Persistence.cs

Related Articles

• Technical overview
• Technical limitations
• Helpdesk business documentation

See Also

• Technical source map
• Architecture overview

Keywords

Logging, observability, correlation, health checks, audit, timeline.

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20