Ignition 8.1
Ignition 7.9
Ignition 7.8
Sepasoft - MES Modules
Cirrus Link - MQTT Modules
Inductive University
Ignition Demo Project
Knowledge Base Articles
Forum
IA Support
SDK Documentation
SDK Examples
You're currently browsing the Ignition 8.0 docs. Click here to view the latest docs.
By default, current alarm data is only stored in memory, and a finite number of events are retained for each alarm. Fortunately, Ignition can easily be configured to store alarm data into a SQL database with an Alarm Journal Profile. The journal can store basic data about alarms that have occurred, such as their source and timestamp, associated data on the alarm, and the values of the alarm's properties at the time the event occurred. The Alarm Journal is used by the Alarm Journal Table component, and can be accessed through scripting functions and direct database queries.
The Gateway can have more than one Alarm Journal. Alarm Journals have options to filter which Alarms are stored in the journal, therefore, by having more than one alarm journal configured on the Gateway, it is possible to store some alarms in one journal, and different alarms in another journal. Once configured, the journal can be accessed by the Alarm Journal Table component, scripting functions, or direct database queries.
Alarm Journals can store data in one of three ways, and store data indefinitely unless a Data Pruning value is set:
It is strongly encouraged to set a Data Pruning value for Internal Alarm Journal Profiles. Otherwise, it could cause your computer to run out of hard drive space.
Configuring an Alarm Journal
You must have an Alarm Journal Profile created and have a valid database connection to use the Alarm Journal Table.
In Ignition, an Alarm Journal stores historical information about alarms in a database. It can store basic data about alarms that have occurred, such as source and timestamp, along with associated data on the alarm, and the values of the alarm's properties at the time the event occurred. You can choose to store your alarm data on an external database or automatically send it to a remote gateway's Alarm Journal to be logged. Both options are described in the sections below.
Create a single Alarm Journal Profile to store all of your alarms, or create multiple journals to store alarms across multiple databases. Each journal stores alarms based on the filters you set up and can prune data automatically after a set time limit.
Look for the blue arrow and click on Create new Alarm Journal Profile.... The Alarm Journal Profiles screen will be displayed.
You have the option of logging alarm journal events to an external database, logging locally, or sending them to a remote gateway's Alarm Journal. In this example, select Database, and click Next. (Configuring alarm journal events to be sent to a remote gateway is addressed in Create an Alarm Journal to Log Events to a Remote Gateway section on this page.
Enter the Name of your alarm journal profile. The default name is 'Journal.' Most of the fields have default settings. Refer to the journal properties table below for setting descriptions, and update as necessary. Click the Create New Alarm Journal Profile button at the bottom of the page. Once completed, the tables will be created for you once an alarm event occurs. 
Using Multiple Alarm Journals
If you only have one alarm journal specified on your Gateway, then you do not need to specify the journal name on the Journal Name property. Ignition will set this for you. If you have more than one alarm journal created, then you need to provide the name of the journal you'd like to query in the Journal Name component property of the Property Editor.
Just like configuring alarm journal events to be logged into a database, it is done from the Gateway Webpage, Config > Alarming > Journal.
To have your alarm journal events automatically sent to a remote gateway's alarm journal, select Remote, and click Next.
If an Alarm Journal exists on the remote gateway, the fields will autopopulate. The name of the gateway and the Alarm Journal Profile name will appear in the Name field prefaced with the alarm journal profile name,(i.e., Ignition_Test_Journal), as shown in the following example. Click Create New Alarm Journal Profile. 
You will receive a successful message stating your new Alarm Journal Profile was created.
Main | |
|---|---|
Name | The default name, is the name of the Remote Gateway and Alarm Journal. |
Description | Description of the journal profile. Optional |
Enabled | By default. The journal profile is enabled. |
Remote Gateway | |
Gateway Name | Name of the Remote Gateway. |
Alarm Journal | Name of the Alarm Journal on the Remote Gateway. |
Ignition Gateways can now create an Internal Alarm Journal Profile that stores Journal entries locally.
Go to the Gateway webpage, Config > Alarming > Journal to create the Internal alarm journal profile.
Main | |
|---|---|
Name | The default name, is the name of the Remote Gateway and Alarm Journal. |
| Minimum Priority | Only events equal to or greater than the specified priority will be stored. |
Description | Description of the journal profile. Optional |
| Stored Shelved Events | If enabled, events generated by "shelved" alarms will still be written to the journal system. Default is false. |
Enabled | By default. The journal profile is enabled. |
Because the Alarm Journal uses a SQL database to log alarm events, any application that has access to the database can retrieve journal data. Alarm events can be made freely available outside of Ignition, and integrated into other software packages. Additionally, other applications can write to the same tables, so Ignition applications can monitor activity in other systems.
While a SQL query will return data from the journal, the Alarm Journal Table component will automatically do so without manually writing a query. The component can filter on both Display Path and Source Path, as well as Date Range. The component can be configured to a single Journal Profile, so multiple instances of the component in the same project may look at different profiles.
More information on this component can be found on the Alarm Journal Table Component page.
Main | |
|---|---|
| Name | The default name is Journal. |
| Description | Description of the journal profile. |
| Enabled | By default. the journal profile is enabled. |
| Datasource | This is the ONLY required setting which must be a valid database connection. Events are stored to this datasource. |
| 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. |
| 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. |
Stored Event DataAlarm events consist of two main types of data: the primary information about the alarm, such as transition state, time, etc. , and the 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 | |
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:
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 that 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 |
The Alarm Journal system will automatically create the necessary tables for you, and scripting functions can be used to query the system without having to know about the table structure. However, understanding the structure of the Alarm Journal tables can be useful for accessing the data in situations where SQL queries are more convenient.
alarm_events)This table stores the core data for each event that occurs. An event is a transition for an alarm between active, cleared, or acknowledged. Additionally, other events may be stored in this table that aren't directly related to an alarm, such as a system shutdown event. This table defines a primary key "id", that is used as a foreign key by the Alarm Event Data table, which stores additional information for each event.
Column Name | Data Type | Description |
|---|---|---|
| id | integer | A unique integer id for each event entry event |
| eventid | string | The UUID of the alarm event. |
| source | string | The qualified path of the entity that generated the alarm event. See below for more information about qualified paths. |
| display path | string | The value set for the "Display Path" of the alarm. Generally a user defined, friendlier version of the source. |
| priority | integer | The priority or severity of the alarm: 0: Diagnostic |
| eventtype | integer | The type of transition represented by this event: 0: Active |
| eventflags | integer | A numeric bitmask flag field providing additional information about the event. Bit 0: System Event - One of the designated system events. (System Startup, System Shutdown) |
| eventtime | datetime | The time of the event. |
This table stores the properties associated with an alarm event. The individual event is referenced through the ID column, against the alarm event table.
Column Name | Data Type | Description |
|---|---|---|
| id | integer | The id that corresponds to the alarm event in the alarm_events table. |
| propname | string | The name of the property. May be one of the common alarm properties (a configuration setting), or the name of an associated data property. |
| dtype | integer | The data type of the property, indicating which data column should be used: 0: Integer 1: Float 2: String |
| intvalue, floatvalue, strvalue | integer, float (double), string | The corresponding value columns for the property. Unused columns will |
A qualified path in Ignition is a path to an object, described by various annotated components. Each component has a type identifier and a value, separated by a colon (:), and each component is separated by colon-forward slash (:/). For example, an alarm is identified by alm:Alarm Name. It usually exists under a Tag, in which case, its fuller path would be tag:Path/To/Tag:/alm:Alarm Name. Paths can be built up further depending on the level of specificity required by the situation.