# Simplifying Source Path for Alarms **URL:** \ **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:** 8\ **Page:** 1
**Author:** ![arpit\_arun\_kumaar](https://avatars.discourse-cdn.com/v4/letter/a/ecccb3/32.png) [@arpit\_arun\_kumaar](https://forum.inductiveautomation.com/u/arpit_arun_kumaar)\ **Post date:** [March 1, 2024, 7:58pm UTC](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698/1 "2024-03-01T19:58:11Z")
I am running Ignition v8.1.37. On my alarm status table, I wish to simplify the way the source path is displayed. For instance, currently for all of my tags, the source path is represented as: prov:default:/tag:TagPath:/alm:Message. I am looking for a way to just display something just the TagPath in that column. I was thinking of a way using custom parameterized expressions or something but couldn't get far with that. ---
**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\ **Post date:** [March 29, 2024, 6:52am UTC](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698/2 "2024-03-29T06:52:18Z")
Did you add a display path to your alarm? ---
**Author:** ![David\_Rodriguez](https://avatars.discourse-cdn.com/v4/letter/d/b5e925/32.png) [@David\_Rodriguez](https://forum.inductiveautomation.com/u/David_Rodriguez)\ **Post date:** [October 31, 2024, 2:47pm UTC](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698/3 "2024-10-31T14:47:46Z")
Anyone found a solution for this? Currently having the same challenge here. I am already using DisplayPath to display the department responsible to look at the alarm. I would really need to simplify the source path to something more readable ---
**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\ **Post date:** [October 31, 2024, 4:17pm UTC](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698/4 "2024-10-31T16:17:22Z")
I'd suggest creating a new topic. ---
**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")
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… ---
**Author:** ![David\_Rodriguez](https://avatars.discourse-cdn.com/v4/letter/d/b5e925/32.png) [@David\_Rodriguez](https://forum.inductiveautomation.com/u/David_Rodriguez)\ **Post date:** [October 31, 2024, 7:20pm UTC](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698/6 "2024-10-31T19:20:56Z")
Hi Andrews, sorry I am a bit new. Do you mean a new property for the alarm? Like a custom property? ---
**Author:** ![David\_Rodriguez](https://avatars.discourse-cdn.com/v4/letter/d/b5e925/32.png) [@David\_Rodriguez](https://forum.inductiveautomation.com/u/David_Rodriguez)\ **Post date:** [October 31, 2024, 7:25pm UTC](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698/7 "2024-10-31T19:25:00Z")
Thank you very much Irose. Indeed what I am trying to achieve is that my email notification instead of displaying: > "AL006" at "prov:default:/tag:Tiofarma/OB/HB1/Preparation\_weighing\_CZV/0210\_TubeFiller1/AL006/AL006:/alm:AL006" became active at 04:51:06 That they display something like: > "AL006" at "0210\_TubeFiller1" became active at 04:51:06 Thank you very much for your guidance ---
**Author:** ![richardNZ15](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/richardnz15/32/33373_2.png) [@richardNZ15](https://forum.inductiveautomation.com/u/richardNZ15)\ **Post date:** [April 8, 2026, 9:46pm UTC](https://forum.inductiveautomation.com/t/simplifying-source-path-for-alarms/86698/8 "2026-04-08T21:46:50Z")
The alarm properties “Label” and / or “Display Path” can be used to define nicer messages for the alarm to display, both in the alarm status tables and in email notifications.