Issue
These alarms can flood the Alarm Viewer during device offline events, power outages, or heavy system load.
Users want to hide, filter, or suppress these alarms without losing visibility of higher‑priority alarms.
Product Line
EcoStruxure Building Operation
Environment
Building Operation WorkStation and Webstation
Cause
“A Log Sample Was Missed” alarms occur when:
- A device or interface goes offline
- The system is busy, impacting sample collection
- The log configuration is too frequent or uses small COV thresholds
- Power outages cause large numbers of logs to be missed simultaneously
- Existing system alarms are not yet reprocessed after Alarm Decorations are applied
These alarms are system alarms and cannot be disabled at the log object itself.
Resolution
Option 1 — Disable Trend Log when Device is Offline
To prevent the “Log Sample Was Missed” alarm entirely, configure the Activation variable property of the Trend Log.
Steps
- Open the Trend Log → Basic tab
- Find Activation
- Bind Activation to one of the following (in priority order)
- DeviceChanged property of the device
- Any property that reliably indicates online/offline
Expected behavior:
- When device goes offline → Activation = False
Trend collection stops → No “log missed” alarms - When device comes online → Activation = True → Logging resumes
Note:
Trend log Activation does not accept certain binding types (e.g., Device Status) in some EBO versions. If a property is not accepted, use DeviceChanged instead.
Option 2 — Hide or Manage the Alarm Using Alarm Decorations
Alarm Decorations can override default behavior for system alarms and automatically move these alarms to the Hidden Alarms section.
Steps (WorkStation):
-
Open WorkStation and navigate to:
System → Alarms → Alarm Decorations -
Click the “+” icon to add a new Decoration Rule.
-
Create a rule targeting the system alarm:
- Field: System Alarm ID
- Condition: Equals
- Value: The ID for “Log Sample Missed”
-
Set Decoration Actions:
- Auto-hide Override: True
- Priority Override: (Optional) lower to non-operational priority
- Category Override: (Optional) assign to a “System Alarms” category for filtering
-
Apply the rule.
-
Important: Existing alarms will not move until they are reprocessed.
Do one of the following:- Acknowledge existing alarms
- Wait for the alarm to occur again naturally
- Trigger a new test condition to generate a fresh sample-missed event
Expected result: New “Log Sample Missed” alarms appear in Hidden Alarms, not in the main alarm list.
Option 3 — Use Standard Alarm Filters (Works in both WorkStation and WebStation)
Some versions (e.g., EBO 4.0) may not show an Exclude option in Custom Alarm Views, but the standard alarm filter still supports filtering.
Steps (WorkStation)
- Open the standard alarm viewer.
- Right‑click inside the alarm list area.
- Select Add Filter.
- Choose Exclude for System Alarm ID.
- Enter the ID for “Log Sample Missed”.
- Apply and save.
Webstation
In WebStation’s filter dialog, if wanting to hide/ exclude alarms within a specific Priority range, select “Not between”.
Because,
“Between” = show only alarms inside the range
“Not between” = show only alarms outside the range (i.e., exclude that range)
The above steps hides the alarms from this view without requiring Alarm Decorations.
Option 4 — Disable Individual Alarms Manually
- When the alarm appears, right‑click → Disable.
- The specific log’s alarm will no longer reappear.
Option 5 — Reduce Log Load to Prevent the Alarm Triggering
If alarms occur frequently for many logs:
- Reduce the log sampling frequency.
- Increase COV thresholds.
- Investigate field device communication issues.
- Check for overloaded AS or network issues.