Network & Infrastructure / Telemetry, Capacity & Incident Analysis
Interface index changes and misleading historical continuity
After a switch upgrade, one graph appears to inherit another port's traffic history. Interface indices or exporter labels may have changed while the dashboard assumes stable identity.
Environment and inputs: Network and infrastructure observability; Prometheus examples describe metric semantics rather than a universal exporter schema. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Compare interface index, name, description, physical mapping and inventory identifiers before and after the event. Inspect which labels define the stored time series and dashboard joins.
Explain the result
A numeric interface identifier can be stable only within a particular device lifecycle or implementation. Reusing it across changed mappings can merge unrelated operational histories.
Plan the fix
Choose a documented identity strategy that preserves physical and logical context and handles renaming deliberately. Avoid assuming descriptions are unique or immutable without inventory controls.
Check the result and rollback
Validate port-specific counters against known traffic after reboot and upgrade. Restore prior joins if the new scheme duplicates interfaces or loses the ability to trace a historical port mapping.