Can Non-Events monitor data quality issues, not just volumes?
YES - use Search Field filtering in Log Views + threshold detection. Examples:
Detect large messages: Log View "API Responses >10MB" (Search Field: Message Size >10485760 bytes), Non-Events Max 10 occurrences/day (alert if >10 large messages, investigate bandwidth impact).
Detect failed transactions: Log View "Payment Failures" (Search Field: Status Code = "Failed" OR "Timeout"), Non-Events Max 50 failures/hour (>50 = payment gateway issue, alert operations).
Detect duplicate messages: AckNak "Order Submissions with Duplicate Confirmations" (Request: Order Number, Response: Order Number, Max Expected Responses per Request = 1), alert if any Order Number receives >1 Confirmation (data quality issue, idempotency failure).
Detect missing mandatory fields: Log View "Orders Missing Customer ID" (Search Field: Customer ID = null OR empty), Non-Events Max 0 occurrences (zero tolerance, any order without Customer ID = data validation failure).
Detect SLA violations: Log View "Long-Running Transactions" (Search Field: Processing Duration >60 seconds calculated from Start/End timestamps), Non-Events Max 100/day (>100 slow transactions = performance degradation).
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.