Skip to content
English
  • There are no suggestions because the search field is empty.

How do I suppress alerts during a specific time window?

In Statseeker, suppressing alerts on a daily schedule isn’t done directly inside a single “alert rule” toggle—you achieve it through Event Management filters / maintenance-style suppression windows.

Here’s how it works in practice with Event Management:


Core idea

Statseeker alerting pipeline is:

Threshold/Event → Event Management → Alert action

So to “suppress alerts on a schedule,” you:

  • let the event still occur
  • but use Event Management to discard or suppress it during certain times

Scheduled suppression via Event Management (Discard Filter)

1. Go to Event Management

  • Admin Tool → Alerting & Event Management → Event Management

2. Create a new Event Filter

  • Add a filter rule
  • Match the events you want to suppress:
    • Event type (threshold, SNMP, etc.)
    • Device/group
    • Severity (optional)

3. Set the action to suppress

  • Choose:
    • Discard Event (completely suppress alert + logging), or
    • Do not alert (if you still want event visibility but no notification)

4. Apply a time-based schedule (key step)

In the filter configuration:

  • Add a time condition / schedule
    • Example:
      • Days: Mon–Fri
      • Time: 00:00–06:00

This acts like a daily suppression window

👉 During that window:

  • Matching events are suppressed
    👉 Outside the window:
  • Alerts behave normally

5. Save and order the filter

  • Event filters are processed top-down
  • Make sure your suppression rule is above general alert rules

🧠 Important behavior notes

  • Suppression does not stop polling or threshold evaluation
  • It only affects event processing / alert generation
  • If you use “discard,” the event is completely dropped
  • If you use a softer action, you can still:
    • log it
    • report on it later

⚠️ Common pitfalls

  • ❌ No schedule defined → filter always active (everything suppressed)
  • ❌ Wrong filter order → rule never hit
  • ❌ Too broad match → suppresses more than intended
  • ❌ Using threshold config instead of event management (no scheduling there)

🧩 Alternative (less common)

If you need more complex schedules:

  • Use multiple filters (e.g., weekday vs weekend)
  • Or adjust via cron-like external automation (rare)

👍 Example use case

Suppress interface-down alerts every night:

  • Match:
    • Event Type = Interface Down
    • Group = Access Switches
  • Action:
    • Discard
  • Schedule:
    • Daily 22:00–06:00

Event Management Documentation