Is it possible to give the system events a display path like system instead of an empty string?
I would like to set some filters on our Alarm Journal so I can use a second Journal, but I feel that would filter out the system events. Unless it's possible to filter on an empty string?
Alarm journal where?
System generated events have a creatively named isSystem property available you can use for filtering.
Gateway? Not sure what you mean.
Can I use the isSystem property in the Alarm source or display path filters? I suppose I could use this evt:System Startup in the source filter. But, if I choose to use Source and Display path filtering,
Is there a way to use both so that I could filter where displaypath = 'Line1' OR source = 'system'?
If I am reading the filtering description properly, and the video is true, then each filter filters like this: where displaypath = 'Line1' AND source = 'system'.
I want to be sure I understand exactly how I can filter alarm events to the Journal before I make changes, because we have only one Journal setup for the entire plant and I don't want to miss something critical!
Ah, okay, I wasn't sure if you were referring to one of the components in Vision/Perspective (which have access to the underlying objects to filter) or the raw component configuration. Moving this filtering to the components might be your path forward.
Most important thing first:
I'd highly recommend setting up a new alarm journal (you can use the 'local' type) for testing, before you touch your main configuration.
That said:
My understanding from the code (admittedly the description is a bit ambiguous) is that successive filters (comma separated) within a single property are OR-ed together.
However, the source filter is AND-ed with the display path filter, and that is AND-ed with the display path or source filter.
I have a new Journal started, but I am not sure how to test it without making changes to the main Journal. Currently there are no filters on the main Journal, so, if I understand correctly, in order for the new Journal to capture anything, I would have to set filters on the main Journal so it doesn't take everything. Does that sound right?
Now, if there were an option in the tag alarm properties to choose which Journal to use, that could be useful for development.
With multiple Journals, would one Alarm table or Journal component be able to see alarms from all the alarm journals by default?
You don't pick journals like you pick history providers. All alarm events are always delivered to all journals, and it is up to the journal's settings which events it wants to log or not. So if you have a second alarm journal configured with the same filters as the first, each new event that happens will be logged to both journals.
On the individual journal table components you do have to pick a particular alarm journal to query information out of.
Found it:
https://docs.inductiveautomation.com/docs/8.1/platform/alarming/alarm-journal
Data Filters
The three data filter properties (Filter by Alarm Source, Filter by Display Path, and Filter by Display Path or Source) 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 Filter properties, then an alarm must match the configuration on all three 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.
Also, just ran a test, using an empty string like "" does not allow for capturing any alarms without a display path.
