# Ignition Edge remote history provider for displaying data on central Ignition gateway

**URL:** <https://forum.inductiveautomation.com/t/ignition-edge-remote-history-provider-for-displaying-data-on-central-ignition-gateway/115781>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [May 30, 2026, 8:25am UTC](https://forum.inductiveautomation.com/t/ignition-edge-remote-history-provider-for-displaying-data-on-central-ignition-gateway/115781 "2026-05-30T08:25:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fran\_Dujmovic](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/fran_dujmovic/32/70280_2.png) [@Fran\_Dujmovic](https://forum.inductiveautomation.com/u/Fran_Dujmovic)\
**Post date:** [May 30, 2026, 8:25am UTC](https://forum.inductiveautomation.com/t/ignition-edge-remote-history-provider-for-displaying-data-on-central-ignition-gateway/115781/1 "2026-05-30T08:25:02Z")

</div>

Hello everyone,

I'm not certain what the best approach for this matter would be and I haven't found any solutions for my issue on other similar posts.

I have 3 Edge gateways that log historical data in their respective Edge historians. I've set them up as remote tag providers to my central standard Gateway and wanted to use remote history providers to log/display history data on my main Gateway.

I'm using Postgres to store historical data on my central Gateway and querying the data using Named Queries. My issue is that my central gateway doesn't have either the Tag Historian or SQL Bridge modules licensed, which results in data being queried from my remote history providers to just return empty datasets.

My question is what the proper approach for something like this would be? Is it possible to query Edge RTP history data from my central gateway without the aforementioned licensed modules? Am I overlooking something or is this an issue with my system architecture?

---

<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:** [May 30, 2026, 3:13pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-remote-history-provider-for-displaying-data-on-central-ignition-gateway/115781/2 "2026-05-30T15:13:09Z")

</div>

> [@Fran\_Dujmovic](#):
>
> doesn't have either the Tag Historian

You need the Tag Historian module in your central gateway.

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [May 31, 2026, 6:09am UTC](https://forum.inductiveautomation.com/t/ignition-edge-remote-history-provider-for-displaying-data-on-central-ignition-gateway/115781/3 "2026-05-31T06:09:17Z")

</div>

Edge gateway can store history for only a short period of time. Do you require \>1 month pf historical data access?

If so, Edge Sync to a gateway w/ licensed historian is your best bet (while possible, I would try to avoid a custom historian solution...).

If not, you can query the Edge gateways directly, provided your remote tag provider is configured correctly to retrieve history via Gateway Network.

---

<div class="post-metadata">

**Author:** ![Fran\_Dujmovic](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/fran_dujmovic/32/70280_2.png) [@Fran\_Dujmovic](https://forum.inductiveautomation.com/u/Fran_Dujmovic)\
**Post date:** [May 31, 2026, 7:32am UTC](https://forum.inductiveautomation.com/t/ignition-edge-remote-history-provider-for-displaying-data-on-central-ignition-gateway/115781/4 "2026-05-31T07:32:29Z")

</div>

I'm fine with Edge storing data for \<1 month.

> [@Chris\_Bingham](#):
>
> If not, you can query the Edge gateways directly, provided your remote tag provider is configured correctly to retrieve history via Gateway Network.

This is the first approach I've tried. I've set up an Edge instance to have an outgoing connection to my central Gateway, set up a remote tag provider to retrieve historical data via Gateway Network and configured a remote history provider in which I had to disable 'allow storage' (the status was 'read-only' after that - I'm assuming that's because of the lack of the historian license).

In my designer I can see the remote tag provider and tags just fine, but I'm not sure as to how I would query historical data - all of my attempts just return blank. I've tried resetting the trial for another 2 hours, after which everything works as intended and my history data is being displayed properly.

Am I missing something or is this purely a license issue, as Phil mentioned previously?

---

<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:** [May 31, 2026, 1:48pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-remote-history-provider-for-displaying-data-on-central-ignition-gateway/115781/5 "2026-05-31T13:48:45Z")

</div>

> [@Fran\_Dujmovic](#):
>
> purely a license issue

Your central gateway will simply not perform history operations without a license.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [May 31, 2026, 2:18pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-remote-history-provider-for-displaying-data-on-central-ignition-gateway/115781/6 "2026-05-31T14:18:36Z")

</div>

> [@Fran\_Dujmovic](#):
>
> SQL Bridge module

There's a common misconception that this module is needed for connecting to a database or performing queries etc. This is incorrect. This module simply offers a graphical interface for setting up custom database tables and to insert data into them automatically for example on tag trigger. However all of the functionality it offers, and more, is easily implemented in scripting. You might start with this module, but in my experience you will quickly outgrow it
