All child AssetWorX instances connect to their event sources as usual.
Typically, the Master AssetWorX does not connect to event sources directly, but only to the distributed child AssetWorX instances.
The Master connects automatically, if events are enabled.
The Master just needs to be configured to know what event fields to ask its children for. This is done in three steps:
In a child AssetWorX, on the “General settings and subscriptions” dialog, click the “Save fields to clipboard” button.
Save the clipboard content to a text file and transfer it to the Master AssetWorX computer.
On the Master AssetWorX computer, put the file content into the clipboard and click the “Restore fields from clipboard” button.
Alarm/Event notifications coming from child AssetWorX instances do not pass through the Rules Engine.
The Master AssetWorX does do regular counting of the notification coming from child AssetWorX instances though, so it could contain different counters than the child AssetWorX instances.
Each node in the Tree View also acts as an alarm source.
Only "real" levels (and their direct Equipment Properties) of the Tree View contribute with alarms to the Tree View.
"Virtual" and "Filter" levels only aggregate their children.
Complex alarm and event processing is done on a separate CPU thread in the AssetWorX Point Manager so that it does not interfere with normal AssetWorX operation.
AssetWorX exposes these performance counters:
|
Counter Name |
Description |
|
Events input/sec |
Events per second coming into AssetWorX |
|
Events output/sec |
Events per second going out of AssetWorX |
|
Events processing load % |
The CPU load of the event processing part of AssetWorX |
|
Events input queue length |
The number of events waiting in the input queue to the Rules Engine. This should remain at zero or could raise for a short period of time (in the case of an input leak). |
|
Events cache size |
The number of events and alarms that are currently in an abnormal state, and being cached in the AssetWorX memory. |
Historical alarms are not supported.
See Also:
Distributed Asset Catalog Runtime
General Settings and Subscriptions