PI Tag data lineage (or Tag Genealogy)

As a PI System Administrator managing a large system composed of hundreds of interfaces and millions of data points, I currently lack a unified view of the data path for a specific PI Tag. When PI Tag is stale or "stuck," troubleshooting requires manually hopping between multiple Data Archives and Interface nodes to trace the source, which is time consuming and prone to errors.

For example, when a tag like TagA on PIServerX stops updating, troubleshooting requires a manual, multi-step investigation across various Interface nodes and Data Archives to trace the data's origin. This feature should programmatically map the entire data path, showing that TagA arrives via a PI-to-PI Interface from sTagA on ServerY, which in turn pulls from a PI OPC Interface on ServerZ. By providing this end-to-end "hop-by-hop" transparency, the system would allow me to instantly pinpoint whether a failure exists at the source sensor, the intermediate OPC intf, or the final PItoPI interface, transforming a complex manual audit into a streamlined, visual diagnostic process.