Path Mappings
Configure path mappings for telemetry data
0 mappings
| Canonical Key | Sources | Transform | Unit | Category | Tier | Deadband | Precision | Mono | Scope | Actions |
|---|---|---|---|---|---|---|---|---|---|---|
| Loading mappings... | ||||||||||
Add Mapping
⚠️ System Default — read-only here. Saving creates an override at the scope you choose below. To change the default itself, edit
reference-data/ in the auth-service repo.Inherited Values (click to use)
Delete Mapping?
Are you sure you want to delete this mapping?
⚠️ Warning: Vessels inheriting this mapping will fall back to the default.
📡 Discovered Paths
Select a vessel
Click "Discover Paths" to scan vessel telemetry
📉 Output-field shadow
A what-if, nothing is saved: the list each vessel would get from what it sent over the last 14 days, and what a limit on keys per vessel would cut. Hover a heading for what it means.
☑️ Output fields
Tick the keys this list sends to the cloud. Once lists are enforced, an unticked key stays on the boat; locked keys are always sent. Nothing changes until you press Save.
always sent locked, or a notification: no list can stop it held back the vessel holds it back from the cloud critical a critical-heartbeat key unsaved change · no such reading there