Skip to main content

Performance Troubleshooting Decision Tree

Symptoms​

Start with the closest primary symptom.

Scope​

Client, service, dependency, persistence, messaging, and compatibility classification.

Cause​

Likely causes​

The detailed branch pages enumerate source-backed causes.

Safe diagnostic steps​

  1. Select the primary symptom.\n2. Follow its branch.\n3. Open the linked detail page.\n4. Stop where ownership or recovery is not confirmed.

Resolution​

Safe resolution​

Use only the safe resolution on the detailed page.

Validation​

Verify through supported reads and sanitized evidence.

Evidence to collect​

Collect only environment category, time window, capability/route, status or error category, sanitized correlation reference, lifecycle state category, and recent approved change context.

Escalation​

Use the boundary owner shown below.

Source References​

  • microservices/src/performance-service/Program.cs
  • microservices/src/performance-service/Api/PerformanceEndpoints.cs
  • microservices/src/performance-service/Application/Commands/AppraisalCommands.cs

Summary​

This Draft page provides non-destructive, source-backed diagnosis and explicitly stops where recovery authority is not confirmed.

Audience​

Performance users, support, operations, engineering, QA, architecture, security, and implementation teams.

Overview​

Use supported reads and sanitized evidence. Never expose personal/evaluation content, credentials, configuration values, infrastructure details, or operational commands.

See Also​

Keywords​

  • Performance troubleshooting
  • Safe diagnostics

Revision Information​

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