Skip to main content

Performance Health and Observability

Summary​

The runtime exposes a framework health endpoint and a tenant-scoped health-data read. Shared observability and correlation middleware are registered. Workflow failures and outbox relay iteration failures are logged; audit/timeline data provides business evidence.

Health does not prove Workflow availability, successful publication, Notification completion, compatibility parity, or lifecycle correctness. No Performance-specific alert thresholds, dashboards, service objectives, trace sampling policy, or on-call runbook were found.

Safe evidence categories are time window, environment category, operation, status category, correlation reference, and dependency category—never review content or personal data.

Safety and confirmation boundary​

No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.

Source References​

  • microservices/src/performance-service/Program.cs
  • microservices/src/performance-service/Api/PerformanceEndpoints.cs
  • microservices/src/performance-service/Infrastructure/WorkflowServiceClient.cs

See Also​

Keywords​

  • Performance operations
  • Safe support guidance

Revision Information​

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