Skip to main content

⚡ Events

Events are Chipper's way of capturing meaningful activity from your logs.

Once a rule matches your log data, it generates an event. Events act as the bridge between raw logs and alertable conditions.

🧠 What Triggers an Event?​

Events are generated when:

  • A log line matches the filter criteria defined in a rule
  • Chipper detects a pattern like a method starting, ending, failing, or timing out
  • A predefined system event (e.g., sample idle, barcode failure) occurs

🔗 Events → Thresholds → Alerts​

Events by themselves don't trigger alerts — they feed into thresholds.
Once a threshold is breached (like “3 events in 5 minutes”), Chipper triggers an alert.

🔍 How to View Events​

You can:

  • See matching events live in the Rule detail page
  • Preview historical events before saving a new rule
  • Use events as inputs for building custom alerts or dashboards

🛠 Why Events Matter​

Events are how Chipper helps you reason about activity without parsing logs line-by-line.
They power everything else: alerts, charts, history, and long-term reliability tracking.