Skip to main content

Workflow Logging and Observability

Summary​

Workflow uses shared-kernel structured console logging, request tracing and correlation, plus domain-focused audit, timeline, health and outbox views.

Observability flow​

Logging​

Logging providers are replaced with structured console output. The Workflow-specific explicit log call is a warning when an outbox relay iteration fails.

Tracing and correlation​

Shared observability instruments ASP.NET Core and HTTP clients. Exceptions are recorded on server traces. Correlation middleware maintains a request correlation value. Trace exporters are configuration-dependent.

Diagnostics​

The service maps a basic health check and a tenant-scoped summary. Audit, timeline and selected outbox metadata are queryable through Workflow endpoints.

Limitations​

No Workflow-specific metrics, activity source, dashboards, alerts, SLA probes or business-execution logs were found. Operational feeds lack backend authorization.

Requires Confirmation​

Exporter enablement, correlation propagation through messaging, retention, alert thresholds and service objectives require confirmation.

Source References​

  • microservices/src/workflow-service/Program.cs
  • microservices/src/workflow-service/Messaging/OutboxRelayHostedService.cs
  • microservices/src/workflow-service/Application/Queries/WorkflowQueries.cs
  • microservices/src/workflow-service/Infrastructure/Persistence.cs
  • microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
  • microservices/src/shared-kernel/Middleware/CorrelationIdMiddleware.cs

See Also​

Keywords​

Workflow architecture, approval engine, Workflow Service, technical foundation.

Revision Information​

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