Skip to content

Server Aliases

Overview

Server Aliases help Osprey accurately map and track data lineage across systems by resolving different representations of the same PI Server.

In many enterprise environments, a PI server might be referred to by multiple names such as a hostname, IP address, or domain alias. Without normalization, lineage and data quality tools may treat these as separate systems, resulting in broken or incomplete relationships.

Why It Matters for Lineage

Tycho Data uses server names to establish connections between:

  • PI Data Archive tags and AF attributes

  • AF attributes and PI Vision symbols

  • Alerts and dashboards across multiple sources

If a PI server is referenced as 10.1.2.5 in one system and na.pi.company.com in another, Osprey would treat them as distinct servers unless you define an alias.

Using server aliases, Osprey can unify these identities and ensure accurate lineage tracing across your environment.

How to Configure Server Aliases

To set up server aliases:

1. Open your appsettings.ini, located at:

C:/Users/<your_user>/Documents/Tycho Data/Osprey/appsettings.ini

2. Add a [server-aliases] section

Each entry maps an alternate name (or IP) to a canonical server name. Example:

[server-aliases]
10.1.2.5 = na.pi.company.com
pi-host.internal = na.pi.company.com

This tells Osprey:

  • Any reference to 10.1.2.5 or pi-host.internal should be treated as na.pi.company.com

  • All lineage relationships, asset mappings, and visualizations will resolve under the canonical name