- 1 minutes to read

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

Use Search Field Expressions to normalize identifiers so one grouped Log View can correlate related events. 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 Expression for Payment Request Message Type and extract /PaymentRequest/TransactionGUID
  2. Create Search Field Expression for Payment Acknowledgment Message Type and extract /PaymentAck/OriginalRequestID
  3. Normalize both values into the same searchable key (for example CorrelationID)
  4. Build one grouped Log View that includes both message types and groups by the normalized key
  5. Validate the grouped Log View result so request and acknowledgment appear in the same group
  6. Configure AckNak using the grouped Log View API URI and set Warning/Error time spans

Advanced correlation: Group by multiple normalized keys when one key is not unique (for example Correlation ID + Merchant ID + Amount).

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.