Ops enables sensors on Junos leaves but never exports them to a collector. What analytics architecture lesson applies?
Select an answer to reveal the explanation.
Short Explanation
Turning on sensors with no collector is like installing smoke detectors that are not wired to anything—the sensing happens, the alarm never reaches the firehouse. Telemetry needs an export path to a collector before dashboards light up. Leaves do not magically email the NOC screenshots.
Full Explanation
Telemetry requires a collection path; enabling sensors on Junos leaves without export does not deliver analytics to operators. Sensors alone do not populate every NOC dashboard without export. Leaves do not email KPI screenshots automatically as a substitute for collectors. Proper export does not disable the QFX data plane. Exam caveat: Architecture checklist: on-box sensors plus transport plus collector plus dashboards. Operational check: Enable a sensor, configure export to the municipal collector, and confirm KPIs appear end-to-end. 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. 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.