IntegrationAdvancedobservabilitytracingcorrelation
Design integration observability with distributed tracing
Real World Scenario
Support cannot trace why order failed across Salesforce MuleSoft SAP in under 5 minutes mean time to diagnose.
Expected Answer
• Correlation ID generated at entry propagated all hops HTTP headers
• OpenTelemetry spans MuleSoft Salesforce Apex
• Structured JSON logging searchable by correlationId
• Dashboard p95 latency per integration path
• Synthetic transaction every 15 minutes alerting on failure
• Runbook linked from alert with query examples
• Post-incident blameless review updating dashboards
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Correlation ID generated at entry propagated all hops HTTP headers Also consider: OpenTelemetry spans MuleSoft Salesforce Apex In practice: Structured JSON logging searchable by correlationId Optimize for scale and operational observability.
Architect Perspective
Without correlation ID, integration debugging is archaeology—invest in tracing at first production interface.