Skip to main content

Helpdesk Monitoring & Diagnostics

Monitoring flow

Signals

The generic health endpoint uses registered ASP.NET health checks; no explicit database, broker, Document Service or Notification Service dependency check is registered. The service-information response exposes service identity, environment and current time.

The Helpdesk health-data endpoint queries counts for categories, priorities, tickets, open tickets, SLA policies and outbox rows and returns a foundation-stage/seeded assessment. It requires tenant context through the database query path. No inspected Helpdesk UI calls this endpoint; it is an API diagnostic surface.

Shared observability clears default log providers and uses structured JSON console logging. OpenTelemetry captures incoming requests and outgoing HTTP calls, records exceptions, and conditionally exports according to configuration. Correlation middleware accepts or creates an identifier, puts it in the response and logging scope.

Limitations

No application metrics, service-level objectives, dashboards for health-data, alerts, dependency readiness, trace search UI or log retention policy were found.

Source References

  • microservices/src/helpdesk-service/Program.cs
  • microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
  • microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
  • microservices/src/shared-kernel/Middleware/CorrelationIdMiddleware.cs
  • microservices/src/gateway-api/Program.cs

See Also

Keywords

Helpdesk, employee service desk, ticket UI, operations, diagnostics.

Revision Information

Draft source-backed documentation reviewed on 2026-07-20; next quarterly review is 2026-10-20.