Skip to main content

Performance Observability

Summary​

Logging, correlation, tracing, audit, timeline, and missing metrics coverage.

Audience​

Engineers, architects, QA, support, security reviewers, and operators working with the Performance module.

Overview​

Shared Kernel composition replaces default logging with structured console logging, attaches service identity, instruments inbound ASP.NET Core and outbound HTTP traces, and propagates correlation identifiers. Performance adds domain audit and timeline persistence.

Confirmed implementation​

  • Correlation identifiers are accepted or generated, placed in request context, returned to callers, and added to logging scope.
  • OpenTelemetry tracing covers inbound requests and outbound HTTP calls.
  • Command paths record audit and timeline entries in the same save boundary.
  • Workflow and outbox failures use structured logging.
  • A service-specific metrics pipeline and business metrics instruments are not registered.

Classification​

Implemented logging/tracing/history with Foundation-level metrics.

Requires confirmation​

Telemetry destinations, retention, dashboards, alerts, sampling, and business metric ownership require confirmation.

Diagram​

See Also​

Keywords​

  • Performance service
  • Observability
  • Draft technical documentation

Source References​

  • microservices/src/performance-service/Program.cs
  • microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
  • microservices/src/shared-kernel/Middleware/CorrelationIdMiddleware.cs
  • microservices/src/performance-service/Infrastructure/Persistence.cs

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-16
  • Review cycle: Quarterly