The city cloud team asks if telemetry replaces the need for on-box 'show' commands. Which balance is correct?
Select an answer to reveal the explanation.
Short Explanation
Central telemetry is the city-wide traffic map; on-box show commands are walking the intersection yourself when something looks weird. You want both—the map for trends and the street-level check for truth. Ripping out either tool makes troubleshooting harder, not smarter.
Full Explanation
Telemetry complements on-box operational commands; centralized analytics and local verification both remain useful for city cloud troubleshooting. Telemetry does not fully replace every on-box show command or justify removing CLIs from Junos. On-box show commands do not fully replace centralized collectors. Neither becomes irrelevant merely because the fabric is cabled. Exam caveat: Use collectors for fleet/history and CLI for authoritative local truth during incidents. Operational check: For one fault, compare collector charts with on-box show outputs and document both in the ticket. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure. In civic data-center operations, record the expected CLI or collector evidence for this concept so the next on-call engineer can validate fabric behavior without re-deriving the design under incident pressure.