ThingWorx Model Definition in Composer > System > Subsystems > Alert Processing Subsystem
Alert Processing Subsystem
The Alert Processing subsystem manages the alert history stream.
Configuration
Alert Settings
Base Type
Default
Notes
Apply Visibility Checks on Alert Queries
BOOLEAN
true
If set to true, you only see alerts for things to which you have visibility. Queries to the Alert History table will be slower.
Max Queue Size
NUMBER
50000
Only applies to the Neo persistence provider. Sets the size of the queue that writes to the alert history stream. The entries will be rejected once the value is reached.
Data Persistence Provider
PERSISTENCEPROVIDERNAME
ThingworxPersistenceProvider
Persistence provider used to write your stream. If you are using a persistence provider and then switch to a different persistence provider, you should do an export-import to the newly selected persistence provider. If you do not, the history from the initial persistence provider is not included in the new persistence provider; the writes start at the time of the switch.
Analytics Gateway
STRING
N/A
The Analytics Gateway identifies which Analytics Server will be used to evaluate anomaly alerts. A gateway selection is required for anomaly detection.
Do Not Log Active Alerts After Restart
BOOLEAN
false
If this selected, it will not log any entries to the Alert History Stream after restarting the thing.
Was this helpful?