I have an Ignition Gateway with multiple Database Connections to MySQL schemas. Some projects are set to one schema while other projects have their own schema.
The behavior I am seeing is some of my alarms in one schema are being put into the tables of other schemas.
Example:
ProjectA is using database connection A which is tied to the schema A.
ProjectB is using database connection B which is tied to the schema B.
Alarms for ProjectA and ProjectB are ending up in tables alarm_event_data and alarm_events tables in schema B.
My expectation is that alarms for ProjectA would end up in alarm_event_data and alarm_events in schema A however that is not the behavior I am observing.
What I noticed is ProjectA did have alarm_event_data and alarm_events in schema A and then a user created an alarm journal schema B and the tables moved over to schema B.
I assume Ignition is taking care of much of this behavior in the background but I wanted to confirm.
All alarms will go to all Journals, the difference will be in the filter setting of the journal
Example: I have a datasource for items put in bypass. Only items that match that filter actually go to the journal.
1 Like
What Jordan said.
But also, your description suggests you think alarms are part of projects. They are part of tags, which are outside of all projects.
1 Like
Well typically all my projects go to the same database schema. This is the first customer I've seen who is making a new schema for every project (not my recommendation to them).
Is there a way to keep a projects alarms within that projects schema?
No, because alarms aren't associated with projects.
You must use filters in the journals to select the tag hierarchies you think belong to a particular project.
Consider defining a separate tag provider per project. That will simplify the filters.
1 Like
Yes, I know they aren't actually a part of the project. When I say a "project's alarms" I mean the alarms I am associating with a particular project and by extension a "project's schema".
What does that mean? How would Ignition know that you are "associating" an alarm with a project?
Dang. My suggestion was going to be to whoop them like they had dressed up as a piñata for Halloween.
Any way you look at it, though, the filter is what you will need to use to 'define' alarms to a project.
In this screenshot what is causing this particular alarm to be routed to the tables in Schema B versus Schema A?
Nothing there decides where the alarm is journaled. It is an alarm on a tag. It "belongs" to the gateway as a whole, not to a project.
The alarm journal configuration that Jordan pointed out is in the gateway web interface, and dictates what journal is connected to what database. Not related to any project, and not configurable in the designer.
1 Like
I see. That helped make things click in my head.
