# How Things Work - Tag history setting

**URL:** <https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 16, 2023, 2:34pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145 "2023-06-16T14:34:07Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [June 16, 2023, 2:34pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/1 "2023-06-16T14:34:07Z")

</div>

hi  
Let's assume that in tag history settings sample mode is set to tag group and tag group is driven class.  
Is it still possible to record the data on change basis rather than periodic driven rate ?

---

<div class="post-metadata">

**Author:** ![Hayden\_Watson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hayden_watson/32/48792_2.png) [@Hayden\_Watson](https://forum.inductiveautomation.com/u/Hayden_Watson)\
**Post date:** [June 19, 2023, 8:26am UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/2 "2023-06-19T08:26:17Z")

</div>

You can set the tag to store 'on change', but as it only changes with the driven rate, it's functionally the same.

---

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [June 19, 2023, 8:53am UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/3 "2023-06-19T08:53:18Z")

</div>

> [@Hayden\_Watson](#):
>
> but as it only changes with the driven rate

hm any chance you clarify this as i would like to understand that?  
When history recording is on change the "driven tag recording" is not available as an option or i cant see it. By "driven tag" i mean storing only when for example "machine\_on" signal is on.

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/c/2cd45048a3d26d4a7a13616c04b3c5e8d7e57b4f.png)

---

<div class="post-metadata">

**Author:** ![Hayden\_Watson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hayden_watson/32/48792_2.png) [@Hayden\_Watson](https://forum.inductiveautomation.com/u/Hayden_Watson)\
**Post date:** [June 19, 2023, 9:03am UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/4 "2023-06-19T09:03:42Z")

</div>

The driven will dictate when the tag value updates on the Ignition, a direct tag connection will read the PLC every x amount of of seconds, while driven will vary the rate it reads based on your expression.

Storing on change will only store the value when the value changes, if you don't update the value then it won't change, so won't store.

If you want more fine control over when data is stored, you'll want to look into the transaction groups.

---

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [June 19, 2023, 1:46pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/5 "2023-06-19T13:46:27Z")

</div>

Great info many thanks.  
What about scenario where i am setting up history on the tag which is coming from the remote tag provider? I guess in that case "driven" concept does not apply as the tag is controlled by the source tags settings - so i would need to change the settings on that tag to stop updating if the "machine\_on" signal is OFF?

---

<div class="post-metadata">

**Author:** ![Hayden\_Watson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hayden_watson/32/48792_2.png) [@Hayden\_Watson](https://forum.inductiveautomation.com/u/Hayden_Watson)\
**Post date:** [June 22, 2023, 7:13am UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/6 "2023-06-22T07:13:10Z")

</div>

Not sure when it comes to the remote tag providers if you could change it, but if you want to have very fine control of when data is uplaoded you'll want transaction groups set up. Using the SQL Bridge Module

---

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [June 22, 2023, 8:24am UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/7 "2023-06-22T08:24:26Z")

</div>

yes transaction manager would give an ultimate control

---

<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:** [June 22, 2023, 3:34pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/8 "2023-06-22T15:34:35Z")

</div>

You can have the most control by scripting in Gateway Tag Change events.

---

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [June 22, 2023, 5:01pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/9 "2023-06-22T17:01:43Z")

</div>

if i understood -gateway tag change script gives us a coding space to build the logic and then trigger " [system.tag.storeTagHistory](https://docs.inductiveautomation.com/display/DOC81/system.tag.storeTagHistory)" to save history of the data - is it correct?

---

<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:** [June 22, 2023, 5:03pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/10 "2023-06-22T17:03:33Z")

</div>

You can do that, or you can insert data into a database in any way you see fit. You do not have to use Ignitions History module or Transaction Groups at all, so long as you have a full version of Ignition. With Edge, I believe you have to have another module to enable scripting (I'm not sure I do not have edge).

---

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [June 22, 2023, 5:09pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/11 "2023-06-22T17:09:54Z")

</div>

Yes that is a good point. In full gateway we have an ultimate control over data storage to the database as long as it is relational database as ignition does not support time series databases if i remember correctly.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 22, 2023, 5:19pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/12 "2023-06-22T17:19:05Z")

</div>

> [@hewking32](#):
>
> ignition does not support time series databases

You can connect Ignition to anything that has a JDBC driver, pretty easily.

With a custom module, you can do more exotic things like "native" history integration with [InfluxDB](https://inductiveautomation.com/moduleshowcase/module/kymera-systems-inc-influxdb-history-provider) or [Canary](https://inductiveautomation.com/moduleshowcase/module/intellic-modules-llc-chirp-canary-labs-historian-and-html5-dashboard).

---

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [June 22, 2023, 5:23pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/13 "2023-06-22T17:23:44Z")

</div>

thanks for correcting me. i have a full picture now.  
much appreciated

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 22, 2023, 6:21pm UTC](https://forum.inductiveautomation.com/t/how-things-work-tag-history-setting/75145/14 "2023-06-22T18:21:11Z")

</div>

> [@lrose](#):
>
> With Edge, I believe you have to have another module to enable scripting

Even with scripting enabled, you don't get database connections, so no. With Edge, you _must_ use its historian, and either push with sync services or publish to an MQTT broker.
