# Alarm Trend Tag Override Suggestion **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision\ **Created:** [April 18, 2024, 2:13pm UTC](https://forum.inductiveautomation.com/t/alarm-trend-tag-override-suggestion/89048 "2024-04-18T14:13:55Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\ **Post date:** [April 19, 2024, 1:48pm UTC](https://forum.inductiveautomation.com/t/alarm-trend-tag-override-suggestion/89048/4 "2024-04-19T13:48:01Z")
Ok, I think I'm with you now. You basically want a way to overlay alarm points on the trend of whatever tag raised the alarm (within the PLC). Of course the alarm tag itself would still be 1 or 0. I agree, trending the alarm tag itself would be rather useless, especially because the alarm journal exists. The option that I proposed would be a set of _new_ tags within the analog reading UDT (assuming that one exists, which it should). One "alarm value" tag for each alarm that then gets trended. The alarm value is 0 (or, whatever the non-alarm value might be) unless the associated alarm is on. It would look something like this (blue = analog value, magenta = high alarm value) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/9/7996cba869a8b37f85d4f7c8e6acd04d7172e453.png) Or, you can trend the alarm setpoint (assuming that it also exists in the UDT) with a fixed, longer logging interval so the operator can see where it crosses the value. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/3/e3cf7a50a67f797db38adbc51c21f63192bb7c24.png) There's not really a way to put a single point (or a vertical line) on a trend. I think an "associated trend" property for alarms would be difficult to implement, and is unlikely to happen. --- _[View the full topic](https://forum.inductiveautomation.com/t/alarm-trend-tag-override-suggestion/89048)._