A hospital campus already sees device health in Catalyst Center and wants ThousandEyes path data shown beside that health. What should the team do?
Select an answer to reveal the explanation.
Short Explanation
Two notebooks that never share a page force you to flip between stories that are really one incident. Integrate ThousandEyes path data into the Catalyst Center view that already holds device health. A morning spreadsheet, shutting Catalyst Center off, or a second collector that does not share the view leaves the path and the device health apart.
Full Explanation
The campus already has device health in Catalyst Center and wants path data in that same picture. Integrating ThousandEyes path results into the Catalyst Center view places the path beside device health so one incident can be read without a side channel. Copying the path numbers into a standalone spreadsheet every morning preserves a manual extract that never becomes part of the Catalyst Center view the team already uses. Turning Catalyst Center off and keeping only the ThousandEyes dashboard discards the device-health product they meant to keep and replaces a shared view with a single tool. Adding a second collector that never shares its view with Catalyst Center gathers more data in a place the device-health users do not see, which misses the request to put the path beside that health. Exam caveat: integration items are about sharing the view already in use, and shutting the existing product off is not integration. Operational check: open a device in Catalyst Center during a path issue and confirm ThousandEyes path results appear with the device health, rather than only in a spreadsheet or in a collector that does not share the view.