Can I monitor that messages arrive within specific time windows (not just SLA response times)?
YES - use Non-Events with date/time filtering. Financial compliance example: "Monthly invoices must arrive between 10th and 25th of each month, once and only once per customer".
Configuration:
- Log View: "Monthly Customer Invoices" (Search Fields: Customer ID, Invoice Date, Message Type = "Invoice")
- Non-Events resource: "Invoice Monthly Timing Compliance"
- Evaluation interval: Daily (check each day of month)
- Business hours: Days 10-25 of month only (evaluate if current date >= 10 AND <= 25)
- Threshold Min: 1 invoice per Customer ID (alert if zero invoices received for any customer within window)
- Threshold Max: 1 invoice per Customer ID (alert if >1 invoice received for same customer = duplicate/data quality issue)
- Group by: Customer ID (evaluate counts per customer, not total)
Day 9: Non-Events not evaluating (outside window). Day 10-25: Non-Events evaluates daily, checks each Customer ID has exactly 1 invoice. Day 11: Customer A has 0 invoices → Alert fires "Invoice Monthly Timing Compliance: Customer A missing invoice (Day 11 of month, window Days 10-25)". Day 26: Non-Events stops evaluating (window closed). Day 31: Month-end compliance report: 447 customers sent 1 invoice each within window (compliant), 3 customers sent 0 invoices (alerted Day 11-25 for remediation).
Other time window use cases:
- Payroll processing: "Timesheets must arrive Friday 3 PM - Monday 9 AM weekly" (weekend cutoff window)
- Batch file transfers: "EDI files must arrive between 1 AM - 3 AM daily" (overnight processing window, alert if files arrive outside window = scheduling issue)
- Trading settlement: "Settlement confirmations must arrive T+2 days (48-72 hours after trade), not earlier/later" (regulatory requirement)
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.