A university wants Webex call quality to sit next to ThousandEyes path tests so a poor call can be compared with the path. What should be integrated?
Select an answer to reveal the explanation.
Short Explanation
A poor phone call and the road it traveled belong on one map, or you will argue about two different afternoons. Integrate ThousandEyes with Webex Control Hub so call quality sits next to the path tests. A spreadsheet kept apart, turning Control Hub off, or a collector that never shares the view leaves quality and path in different rooms.
Full Explanation
The university wants a poor Webex call compared with the network path taken at the same time, which requires call quality and path tests in one picture. Integrating ThousandEyes with Webex Control Hub so those views sit together is the pairing that does that. A standalone spreadsheet of call scores kept separate from the path tests stores quality away from the path and forces a manual comparison the request was trying to avoid. Turning Webex Control Hub off so only the path-test view remains deletes the call-quality side of the comparison. A second collector that does not share any view with the call-quality data adds path or other telemetry in a silo and never places it next to the Webex quality the university wants to read. Exam caveat: the integration is ThousandEyes with Webex Control Hub. A spreadsheet kept apart, turning Control Hub off, or a collector that never shares the view fails the comparison. Operational check: open one poor call and confirm Webex Control Hub quality and the ThousandEyes path for that interval are visible together, not only in a spreadsheet or in a collector that does not share the call-quality view.