Seasonal Event Interface
This interface helps detect repetitive or expected downtimes by analyzing historical event data over a defined period. This module enables users to fine-tune event handling and suppress alerts that do not require operational attention by identifying patterns such as weekly device shutdowns or routine maintenance windows.
What Do You See on the Screen
This view-only interface presents recurring downtime patterns across selected assets and resources. Users can apply filters (Asset, Resource, Statistic, Time Range) to analyze suppression candidates based on frequency, duration, and matching time windows.
Seasonal Event Suppression | Basic Details
Label
Action
Description / Example
Filters
Asset
Select from the drop-down.
Choose the monitored asset for which you want to analyze recurring event patterns.
Resource
Select from the drop-down.
Select the component or resource under the asset (e.g., Ethernet, Storage).
Statistics
Select from the drop-down.
Choose the relevant performance metric associated with the asset (e.g., Availability, Packet Loss).
Select Time Filter
Select from the drop-down.
Filters the event analysis to a specific timeframe. Example: Current Week, Last Week, Current Month, etc.
Basic Details
Suppression Time
View-only
Displays the recurring time window where the event pattern typically occurs (e.g., every Sunday, 2:00 AM – 4:00 AM).
Asset Name
View-only
Name of the monitored asset from which the event originated.
IP Address
View-only
IP address associated with the asset.
Resource Name
View-only
The specific resource/component within the asset.
Statistics
View-only
The selected metric is used for suppression analysis.
Down Minutes
View-only
Total duration (in minutes) the asset/resource was reported as down during the selected timeframe.
Check
View-only
Number of occurrences or polling cycles checked during the selected analysis window.
Frequency
View-only
Number of times a similar downtime pattern has been observed over the selected window.
Action
View-only
Displays the inference (e.g., "Suppression Candidate") indicating if the recurring pattern qualifies for suppression tagging.
Last updated
Was this helpful?