Skip to main content
Curator automatically prevents the Event Log from being flooded by repeated identical errors or warnings. When the same message occurs many times in a short period, Curator begins suppressing duplicates and periodically logs a summary entry instead. This keeps the Event Log readable and performant without losing visibility into ongoing issues.

​
How it works

  1. First 20 occurrences are always logged — every unique message is allowed through at least 20 times. A full page of identical entries in the Event Log is a clear signal that something is actively failing.
  2. Suppression begins after the 20th occurrence — if the same message keeps appearing, Curator starts holding back duplicates.
  3. Periodic summary entries — rather than silently discarding messages, Curator logs a summary at increasing intervals. Each summary entry is prefixed with [Rate Limited] and includes a count of how many occurrences were suppressed and when they started.
  4. Intervals double over time — summaries appear at 2 minutes, then 4, 8, 16, 32, and cap at every 60 minutes for as long as the issue persists.
Rate limiting state resets after 24 hours of inactivity per message type.

​
What a rate-limited entry looks like

A normal Event Log entry:
Once rate limiting is active, subsequent entries look like this:
The [Rate Limited] prefix is searchable in the Event Log. Use it to quickly find any messages that have been suppressed.

​
Examples

​
Runaway error

Without rate limiting, a continuous error at 2 per second would produce 7,200 Event Log entries per hour. Here is what you would actually see: Result: 7,200 entries/hour reduced to ~26, with each summary carrying the full suppression details.

​
Intermittent error

If the same message appears only occasionally — say, 10 times over 10 minutes — it will never hit the suppression threshold. All 10 occurrences are logged normally and the [Rate Limited] prefix will never appear.

​
Limitations and caveats

  • The Event Log is not a complete audit trail — because suppressed occurrences are not stored, the Event Log should not be used to count how many times something happened or as an authoritative record of security-related events. Use Curator’s Usage Log or an external audit system for that purpose.
  • Some messages are never rate-limited — errors that include dynamic information (such as a user name, record ID, or timestamp) in the message text are treated as distinct messages and are each logged individually, regardless of frequency. This is expected behavior.