# Simplifying Source Path for Alarms

**URL:** <https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [March 1, 2024, 7:58pm UTC](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698 "2024-03-01T19:58:11Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [October 31, 2024, 5:48pm UTC](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698/5 "2024-10-31T17:48:44Z")

</div>

The discussion here, may be of interest to you.

> [@How does system.alarm.queryJournal() query for "source"?](https://forum.inductiveautomation.com/t/how-does-system-alarm-queryjournal-query-for-source/85165):
>
> I haven't been able to find precise details on what the path and source parameters are actually querying against. I want to be exact in my tag alarm queries, because some tag paths are subsets of others (have similar names). So far, I've found the following: "\*Path/To/Tag1\*" returns multiple alarms (ie. Path/To/Tag1 and Path/To/Tag10 both match the former path) "\*Path/To/Tag1:\*" avoides this problem because the source always ends with a colon (apparently) "\*:Path/To/Tag1\*" doesn't return anyt…

---

_[View the full topic](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698)._