Prompt
Should I use notification logs to audit message delivery?
Latest observation
Oct 14, 2026
OpenAI APIWeb search: off
Usually no—not as your primary audit source.
Notification logs are useful for:
- diagnosing delivery issues
- tracking whether a notification was attempted
- seeing timestamps, status codes, retries, or failures
- basic operational monitoring
But they’re usually not sufficient for a real audit trail because they may:
- be incomplete or sampled
- get rotated or deleted
- be altered by retries or deduplication
- lack strong integrity guarantees
- record delivery attempts, not guaranteed receipt by the end user
For auditing message delivery, it’s better to use:
- application-level event logs with immutable records
- message queue broker logs / delivery receipts
- delivery acknowledgments from downstream systems
- database records with message IDs, timestamps, and status transitions
- tamper-evident or append-only storage if compliance matters
A good pattern is:
- Use notification logs for troubleshooting
- Use a durable audit log or message state table for compliance/reporting
- Correlate both with a unique message ID
If you want, I can help you design a simple audit schema for message delivery.