- 2 minutes to read

Non-Events, FAQ, Troubleshooting, Common Questions Non-Events, FAQ, troubleshooting, common questions How do I configure AckNak correlation when Request and Response have different field names?

How do I configure AckNak correlation when Request and Response have different field names?

How do I configure AckNak correlation when Request and Response have different field names?

Use Search Field Expressions to normalize identifiers in both Log Views. Example: Payment gateway workflow:

  • Payment Request message has field <TransactionGUID>abc-123-def-456</TransactionGUID>
  • Payment Acknowledgment message has field <OriginalRequestID>abc-123-def-456</OriginalRequestID>

Solution:

  1. Create Search Field "Correlation ID" for Payment Request Message Type → Extract using XPath /PaymentRequest/TransactionGUID → Store as "CorrelationID"
  2. Create Search Field "Correlation ID" for Payment Acknowledgment Message Type → Extract using XPath /PaymentAck/OriginalRequestID → Store as "CorrelationID" (same field name)
  3. Create Log View "Payment Requests" → Filter by Message Type = "PaymentRequest", display Search Field "CorrelationID"
  4. Create Log View "Payment Acknowledgments" → Filter by Message Type = "PaymentAck", display Search Field "CorrelationID"
  5. Configure AckNak → Request Log View = "Payment Requests", Response Log View = "Payment Acknowledgments", Correlation Field = "CorrelationID" (matches in both views), SLA Timeout = 30 seconds

Advanced correlation: Match on multiple fields (Correlation ID + Merchant ID + Amount) for uniqueness. Match with fuzzy logic (Amount ±$0.01 for rounding differences, timestamps ±5 seconds for clock skew).

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.