Trying to Understand Alarm Journal Gateway Filters

Hello,

I have two tag providers, [default] and [TestPanel]. I’m trying to use two Alarm Journals that filter which alarms it records based on which tag provider I give it. I figured I could do this by changing the filtering settings on the Gateway → Config → Alarming → (My Alarm Journal) → Data Filtering → Source Data filter. I set mine to [TestPanel]* in this case (see pic). I can’t seem to get this to work. system.alarm.queryJournal() does not show any events at all, once I revert the change it shows all alarms again. I’m not sure if I’m missing something from the documentation but their doesn’t seem to be much info on it or examples Alarm Journal | Ignition User Manual . I don’t know if I should be using wildcards either. Does anyone have any info on this? I attached a screenshot showing which specific settings I’m talking about.

This all came about due to change of scope and I figured this would be the fastest way to keep alarms separate while still using system.alarm.queryJournal() due to time left on project. I have some pretty unique constraints for both historian/alarm data retention which is the main reasoning between the split in the alarms (and historian, but unrelated). Preferably I’d find a solution that involves simple filtering like this but I may have to take a step back and redesign some things. Any suggestions would be appreciated.

Edit: Script used

results = system.alarm.queryJournal(journalName="TestPanel_AlarmJournal", startDate = start, endDate = end, state = ['ActiveUnacked', 'ClearUnacked'], includeData=True, includeSystem=False)

I think the right format would be:

prov:TestPanel:*

Why wouldn’t you use the source filter in the journal itself? Or are you trying to segregate the alarms to different storage dbs?

Exactly, one has to be redundant and stored for 1 year, while the other does not need to be redundant and needs to be stored for whatever I choose (2 weeks).

@calimero100582 Thank you, I believe this is working. I will test more tomorrow and mark as solution if so. Does that format come from somewhere, any readings on that in the documentation I can look at?

1 Like

Just what is displayed in the alarm itself, in the tag browser

image

It’s part of a qualified path syntax. More info here:

1 Like

Thanks everyone, this worked and helped me understand it. :slightly_smiling_face: