Main |
---|
Name | The default name is Journal. |
|
Datasource | Events are stored to this datasource. (Only available on Database type profiles) |
|
Enabled | By default. the journal profile is enabled. |
|
Description | Description of the journal profile. |
|
Query Only | When enabled, the alarm journal will not store alarm events. |
|
Use Store and Forward | Enabled by default, which means the alarm journaled events will be stored through the Store and Forward system. If not enabled, they will be stored directly against the database. This system protects data from being lost due to temporary database connectivity issues. (Only available on Database type profiles) |
|
Events |
|
---|
Minimum Priority | Only events equal to or greater than the specified priority will be stored. The default is Low. You can set the priority to be: Diagnostic, Low, Medium, High, and Critical. |
|
Store Shelved Events | Not enabled by default. If enabled, events generated by "shelved" alarms will still be written to the journal system. |
|
Store Enabled & Disabled Events |
The following feature is new in Ignition version 8.1.8
Click here to check out the other new features
When enabled, events generated by enabling or disabling alarms will be stored in the journal. This includes cases where the Enabled property on an alarm is toggled, as well as cases where a Tag's Alarm Eval Enabled property is changed. This property additionally relies on setting the Perspective/Vision Alarm Journal Table properties for the enabled and disabled events. |
|
Event Data |
|
---|
Static Config | By default, it is not selected. If selected, will store the values of static alarm configuration. That is, the alarm properties that are not bound. These do not change during evaluation, only when a user modifies them in the Designer, and so they are not stored by default. |
|
Dynamic Config | If selected, will store the values of dynamically bound alarm configuration properties. The value of these properties can change at any time, and the values at the time of the alarm are captured on the alarm event. |
|
Static Associated Data | If selected, will store the values of non-bound associated data (properties created by the user) properties on alarm that do not change during execution. |
|
Dynamic Associated Data | If selected, will store the values of dynamically bound associated data (properties created by the user) properties. |
|
Data Filters |
---|
Note: The following three properties interact via logical AND, meaning an alarm must meet the criteria for all three for it to be logged in the Journal. Thus, if you supply values for all three Data Filer properties, then an alarm must match the Filter by Alarm Source, Filter by Display Path, and Filter by Display Path or Source properties. Example: If a journal has values for all three properties, and an alarm only meets the requirements for Filter by Alarm Source and Filter by Display Path or Source, but not Filter by Display Path, then the alarm will not be logged to the Journal. If you want to filter on both the Display Path and Source Path, you would want to use only one of the two following approaches: - Filter by Alarm Source and Filter by Display Path
- Only use Filter by Display Path or Source
It is recommended to avoid using all three properties simultaneously on the same Journal.
|
Filter by Alarm Source | Only events matching the source will be stored. Multiple sources to match can be comma separated. Leave blank to store events from all sources. |
|
Filter by Display Path | Only events matching the display path will be stored. Multiple display paths to match can be comma separated. Leave blank to store events from all display paths. |
|
Filter by Display Path or Source | Only events matching the display path, if defined, will be stored. Multiple matches can be comma separated. If no display path is defined, only events matching the source will be stored. Leave blank to store all events. |
|
Data Pruning |
---|
Enable Data Pruning | If selected, data will be deleted after the specified time period as set by the Prune Age and Units below. Default is false.
Note: Since the data is stored directly in a database, an administrator is free to manually delete data at any time.
|
|
Prune Age | The number of Prune Age Units to store data for. i.e., 1 year, 5 hours, etc. The default is 1. |
|
Prune Age Units | The type of Prune Age Unit. Default is Years. You can choose the unit to be Milliseconds, Seconds, Minutes, Hours, Days, Weeks, Months, or Years. |
|
AdvancedThese settings let you specify your own table names. This is especially useful when trying to use multiple alarm profiles within a single database (not common, but can happen, especially with multiple systems sharing a single database). |
---|
Table Name | The table name for the core event table. The default is alarm_events . |
|
Event Data Table Name | The table name for event data associated with alarms. The default is alarm_event_data . |
|