Object configuration Alarm tab
- Last UpdatedJul 19, 2024
- 1 minute read
Use the Alarms tab to enable alarming for various engine-related conditions.
|
Editor Option |
Associated Attribute |
Description |
Runtime Access (Supervisory, User, Read-Only, None) |
|---|---|---|---|
|
Report checkpoint failure alarm |
Engine.CheckPointFailed.Alarmed |
If enabled, an alarm will be triggered when the checkpoint operation fails to checkpoint the last object condition. |
None |
|
Priority |
Engine.CheckPointFailed.Priority |
See Alarm attributes. |
Supervisory, User |
|
Report object quarantined condition |
Engine.ObjectQuarantined.Alarmed |
If enabled, an alarm will be triggered when at least one hosted object is in a quarantined state, indicating a software exception has occurred on the object. If all quarantined objects are later undeployed, the alarm will be disabled. |
None |
|
Priority |
Engine.ObjectQuarantined.Priority |
See Alarm attributes. |
Supervisory, User |
|
Report subscription folding condition |
Engine.Folding.Alarmed |
If enabled, an alarm will be triggered when Message Exchange folding is currently active, which means that this object is overloaded with regards to publishing throughput. Folding occurs when the object detects that a target object is receiving more data than it can process in a timely manner. |
None |
|
Priority |
Engine.Folding.Priority |
See Alarm attributes. |
Supervisory, User |
|
Report scan overrun condition |
Scheduler.ScanOverrun.Alarmed |
If enabled, an alarm will be raised if a scan overrun condition occurs. |
None |
|
Consecutive scan overrun limit |
Scheduler.ScanOverrun.HiLimit |
The maximum number of consecutive scan overruns that are allowed before an alarm is raised. A value of -1 will prevent overruns from being checked against a limit. |
Supervisory, User |
|
Priority |
Scheduler.ScanOverrun.Priority |
See Alarm attributes. |
Supervisory, User |