# Get the Historical Tag Path from the Tag Path

**URL:** <https://forum.inductiveautomation.com/t/get-the-historical-tag-path-from-the-tag-path/61981>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [July 16, 2022, 5:27pm UTC](https://forum.inductiveautomation.com/t/get-the-historical-tag-path-from-the-tag-path/61981 "2022-07-16T17:27:45Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [October 22, 2024, 9:04pm UTC](https://forum.inductiveautomation.com/t/get-the-historical-tag-path-from-the-tag-path/61981/10 "2024-10-22T21:04:01Z")

</div>

> [@pascal.fragnoud](#):
>
> which is not obvious in the case of a remote provider, since the driver will use the name of the provider on the gateway where it lives

See this topic:

> [@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…

Agreed, not obvious. But not difficult. (See example code.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/get-the-historical-tag-path-from-the-tag-path/61981)._