How do I monitor request-response patterns across 3+ systems (not just 2)?
Chain multiple AckNak resources OR use custom correlation. E-commerce 4-system workflow:
- Customer submits Order (E-commerce website) → Generates Order Submission message
- Order validated (Order Management System) → Generates Order Validation message
- Payment processed (Payment Gateway) → Generates Payment Confirmation message
- Fulfillment created (Warehouse Management System) → Generates Fulfillment Order message
Approach 1: Chain AckNak resources
- AckNak #1: Order Submission (Request) → Order Validation (Response), 2-minute SLA, correlation by Order Number
- AckNak #2: Order Validation (Request) → Payment Confirmation (Response), 30-second SLA, correlation by Order Number
- AckNak #3: Payment Confirmation (Request) → Fulfillment Order (Response), 5-minute SLA, correlation by Order Number
Each AckNak alerts independently. Benefit: Pinpoint which system pair failed (if AckNak #2 alerts, payment gateway issue).
Approach 2: Custom correlation with BPM
- Use [Business Process Modeling (BPM)][] to visualize complete 4-system workflow in single view
- Configure Non-Events on BPM completion metric: "Alert if Order Submission sent but no Fulfillment Order within 10 minutes end-to-end SLA" (monitors entire chain, not individual hops)
- BPM correlation requires [correlation ID propagation][] across all 4 systems (Order Number or GUID in all message types)
When to use each: Chained AckNak for granular per-hop SLA monitoring (troubleshoot which system delayed), BPM + Non-Events for end-to-end business SLA monitoring (customer experience focus).
Next Step
Need more help? Check the Troubleshooting Overview for all FAQs, or refer to the Configuration Guide to fine-tune your Non-Events monitoring setup.