# Alarm trend does not work with a nondefault tag provider

**URL:** <https://forum.inductiveautomation.com/t/alarm-trend-does-not-work-with-a-nondefault-tag-provider/9915>\
**Category:** Ignition\
**Created:** [April 15, 2015, 12:35pm UTC](https://forum.inductiveautomation.com/t/alarm-trend-does-not-work-with-a-nondefault-tag-provider/9915 "2015-04-15T12:35:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vita](https://avatars.discourse-cdn.com/v4/letter/v/51bf81/32.png) [@Vita](https://forum.inductiveautomation.com/u/Vita)\
**Post date:** [April 15, 2015, 12:35pm UTC](https://forum.inductiveautomation.com/t/alarm-trend-does-not-work-with-a-nondefault-tag-provider/9915/1 "2015-04-15T12:35:07Z")

</div>

Hi,

I have defined more tag providers. But for tags which are not in the default provider there is no Alarm trend in AlarmStatusTable (exactly displays History not available). Tags are configured same (data type, same history provider, same alarm). Missing I something in configuration ?

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/58a9018fe404fcbe2bb0351daf92d21dedb72407.png)

---

<div class="post-metadata">

**Author:** ![Vita](https://avatars.discourse-cdn.com/v4/letter/v/51bf81/32.png) [@Vita](https://forum.inductiveautomation.com/u/Vita)\
**Post date:** [May 5, 2015, 9:34am UTC](https://forum.inductiveautomation.com/t/alarm-trend-does-not-work-with-a-nondefault-tag-provider/9915/2 "2015-05-05T09:34:01Z")

</div>

Hi,

I could not find a solution for this problem. Does this mean that this is a bug in Ignition? Or it works to someone? Thanks

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [June 3, 2015, 4:38pm UTC](https://forum.inductiveautomation.com/t/alarm-trend-does-not-work-with-a-nondefault-tag-provider/9915/3 "2015-06-03T16:38:43Z")

</div>

Hi,

I believe this should be fixed in 7.7.5. The tag paths were being parsed without including the tag provider.

Regards,