# Remote Tag Provider History Settings with more than two gateways

**URL:** <https://forum.inductiveautomation.com/t/remote-tag-provider-history-settings-with-more-than-two-gateways/95541>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [September 4, 2024, 5:25pm UTC](https://forum.inductiveautomation.com/t/remote-tag-provider-history-settings-with-more-than-two-gateways/95541 "2024-09-04T17:25:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tmahaf](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tmahaf/32/23492_2.png) [@tmahaf](https://forum.inductiveautomation.com/u/tmahaf)\
**Post date:** [September 4, 2024, 5:25pm UTC](https://forum.inductiveautomation.com/t/remote-tag-provider-history-settings-with-more-than-two-gateways/95541/1 "2024-09-04T17:25:24Z")

</div>

Here's the diagram from the documentation

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/8/3866939a103a5dde739bd69752dae76daee1986e.png)

We have remote tag providers on several gateways that our front end sever needs tag historical data from. I want to have the front end gateway query the data directly from database instead of it being routed through the gateway network with our multiple backend gateways housing the tag providers.

Im curious how I might fill in "History Driver" and "History Provider" with multiple gateways and multiple tag providers? Leave them blank?

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

---

<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:** [September 4, 2024, 6:07pm UTC](https://forum.inductiveautomation.com/t/remote-tag-provider-history-settings-with-more-than-two-gateways/95541/2 "2024-09-04T18:07:51Z")

</div>

You might find this discussion helpful:

> [@Remote Tag Provider History Queries](https://forum.inductiveautomation.com/t/remote-tag-provider-history-queries/93632):
>
> I'm working on a couple tasks related to historians and history queries, and have encountered some behaviors of remote tag providers (RTPs) that have me stymied: There's no public way to retrieve the gateway name that a RTP is pointing at, nor any public way to retrieve the far end's real tag provider name. (Reflection has exposed com.inductiveautomation.ignition.gateway.tags.distributed.client.RemoteTagProvider and com.inductiveautomation.metro.api.ServerId to me, and a number of private fie…

FWIW, my new Exchange resource uses the reflection technique, discussed here:

> [@Tag Report Utility](https://forum.inductiveautomation.com/t/tag-report-utility/95299):
>
> New resource just uploaded to the Exchange (pending review). Also available here: [https://www.automation-pros.com/TagReportUtility/](https://www.automation-pros.com/TagReportUtility/) I intend to publish at this link as well as in the Exchange going forward. Announcements will be in this topic. (: Highlights: Provides a Perspective Popup View that provides a user interface to system.tag.query() that entirely replicates the functionality of the Designer's Tag Report Tool. Provides a Perspective Embedded View that provides Time Span selectio…

Fundamentally, you should be using fully-qualified historical tag paths (start with `histprov:`) rather than simple tag paths (start with `[provider]`).