> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/thousandeyes-and-cisco-cloud-control.md). # ThousandEyes and Cisco Cloud Control When managing multiple Cisco products, navigating between different dashboards can disrupt troubleshooting and operational workflows. The Cisco Cloud Control integration embeds the ThousandEyes platform into the Cisco Cloud Control experience. This allows you to access ThousandEyes assurance data and workflows alongside other Cisco networking, security, and collaboration tools, while leveraging centralized access to portfolio-wide capabilities like the Cisco AI Assistant and Cisco AI Canvas. This article outlines the supported functionality, prerequisites, availability, data scope, and ThousandEyes-specific behaviors. For more information about Cisco Cloud Control, see [Cisco Cloud Control](https://www.cisco.com/c/en/us/support/cloud-control/cloud-control/series.html). {% hint style="info" %} This integration is available for eligible ThousandEyes organizations hosted in the commercial US1 and US2 regions. Eligibility is based on the region that hosts the organization, not the user’s physical location. Managed service provider organizations are not supported. The ThousandEyes for Government instance is not supported. {% endhint %} ## Definitions * Tenant: A tenant is a connected Cisco product environment within Cisco Cloud Control. For ThousandEyes, one tenant represents one ThousandEyes organization. * Tenant group: A named collection of product tenants linked to form one cross-product environment. A group can contain one tenant from each supported product, such as one ThousandEyes organization and one Meraki organization. ## Supported Functionality The integration currently supports the following features: * Header and Navigation Integration: You can access the ThousandEyes platform from the Cisco Cloud Control header and navigation menu. You can also pin the ThousandEyes option to your header for quick access. * Full ThousandEyes Navigation: When you open the ThousandEyes platform within Cisco Cloud Control, the complete ThousandEyes navigation menu is available. * User Context Handover: Your user identity, permissions, organization, and account group access are shared between Cisco Cloud Control and the ThousandEyes platform to provide a simplified login experience. * Enterprise Agent Data Sharing: View Enterprise Agent status and configuration details in the Cisco Cloud Control **Inventory**. * Network and Application Synthetics Alert Notifications: View Cloud and Enterprise Agent alerts in the Cisco Cloud Control **Actions** list. * AI Experiences: Access supported ThousandEyes capabilities with the Cisco Cloud Control AI Assistant and AI Canvas. ## Cisco Offer Integrations and Data Handling Cisco Cloud Control allows users to access and manage offerings from across the Cisco portfolio, including the Cisco AI Assistant, Cisco AI Canvas, and customer-enabled integrations like ThousandEyes. When leveraging any Cisco Offer integration, you must review the Offer Disclosure for each integrated Cisco Offer to fully understand how your data is handled across the portfolio. This includes specific details regarding data collection, processing, storage, security practices, retention periods, and any available controls for AI Features. ## Prerequisites The following prerequisites are required for using the integration: * Your ThousandEyes organization leverages Cisco’s shared authentication services to provide a simplified login experience. * Your organization is hosted in the commercial US1 or US2 ThousandEyes region. For information about region assignments, see [ThousandEyes Multi-Region Cloud Support](https://docs.thousandeyes.com/product-documentation/user-management/user-activity/thousandeyes-multi-region-cloud-support). * An admin user within your organization has completed the Connecting ThousandEyes to Cisco Cloud Control steps below. ThousandEyes users who have the Organization Admin role are automatically given the necessary Tenant Full Admin role in Cisco Cloud Control. ## Connecting ThousandEyes to Cisco Cloud Control For instructions on setting up the integration, refer to the [Cisco Cloud Control Getting Started](https://www.cisco.com/c/en/us/td/docs/ai/cisco-cloud-control/articles/cisco-cloud-control-getting-started.html) documentation. Once you connect to the tenant, you will be able to access ThousandEyes application through Cloud Control. ## Getting Started with Cisco Cloud Control ### Universal Header Linked ThousandEyes organizations will see a universal Cisco header, rather than the standard ThousandEyes header. The universal header provides a consistent app launcher and navigation experience across all supported Cisco products. You can still use the standard ThousandEyes navigation menu after you open the platform with Cisco Cloud Control. The universal header includes a theme selector that allows users to choose between **Dark**, **Light**, and **System Default** themes. The user’s theme selection applies across all applications within Cloud Control, including ThousandEyes. {% hint style="info" %} Some parts of the ThousandEyes UI will not have Dark mode available as part of the initial release. If you navigate to a part of the product that does not have Dark mode enabled yet, you will be returned to Light mode for that view. Your Dark mode setting will remain in place for supported parts of the UI. {% endhint %} ### Organizations and Account Groups Cisco Cloud Control tenants are linked on a one-to-one basis to ThousandEyes organizations. Your permissions for that organization will determine whether you can see that data within the Cloud Control interface. For users who have access to more than one ThousandEyes account group, Cisco Cloud Control will show the user data from all account groups you have permissions for. ### Viewing Enterprise Agents in Inventory The Cisco Cloud Control Inventory provides a shared view of supported assets from connected products to simplify asset management. You can view data for ThousandEyes Enterprise Agents that you have permissions to view in the Inventory. This data includes attributes such as the agent name, reachability, status, associated site information, and host serial number (for Cisco devices). Users can view all Enterprise Agents by searching for "ThousandEyes" in the asset search bar. {% hint style="warning" %} The Inventory application does not support editing agent settings. Enterprise Agent deployment and management must be done directly through the ThousandEyes application. {% endhint %} {% hint style="warning" %} It may take up to **12 hours** after tenant linkage for agent data to appear in Cloud Control Inventory. Any subsequent changes to agent status may take up to **one hour** to be reflected. {% endhint %} For more information about filters, assets, and navigating the Inventory, see [Cisco Cloud Control Inventory](https://www.cisco.com/c/en/us/td/docs/ai/cisco-cloud-control/articles/cisco-cloud-control-inventory.html). ### Viewing ThousandEyes Alerts in Actions Supported ThousandEyes alerts appear in the Cisco Cloud Control in-product notifications feed. They map to the Cisco Cloud Control severity levels as follows: * Info -> Info * Minor -> Medium * Major -> High * Critical -> Critical {% hint style="info" %} Cisco Cloud Control notifications for ThousandEyes alerts are in-app only. Cisco Cloud Control does not send a separate outbound notification for ThousandEyes alerts. Existing ThousandEyes notification routes continue to operate independently. {% endhint %} In addition, major and critical severity alerts will also appear as interactive **Actions**. {% hint style="info" %} Info and minor severity alerts can also appear in the **Actions** list if they correlate to higher severity alerts. {% endhint %} {% hint style="warning" %} Cisco Cloud Control only supports ThousandEyes Network and Application Synthetics test alerts. {% endhint %} {% hint style="warning" %} Alert delivery uses batch processing. Alert data changes may take up to an hour to appear in Cisco Cloud Control. {% endhint %} {% hint style="warning" %} Clearing or dismissing an action in Cisco Cloud Control does not affect the ThousandEyes alert. You will need to open the alert in the ThousandEyes platform to investigate or snooze it. {% endhint %} ### Using ThousandEyes Data with the Cisco AI Assistant and AI Canvas The Cisco AI Assistant and Cisco AI Canvas allow you to use natural-language prompts to investigate ThousandEyes monitoring data from Cisco Cloud Control. The Cisco AI Assistant supports approved read and write actions, while AI Canvas can retrieve and analyze ThousandEyes data using any read-only ThousandEyes MCP server tools. {% hint style="info" %} For ThousandEyes MCP server write capabilities, you will need to use the public ThousandEyes MCP server, rather than prompts through Cisco AI Canvas. {% endhint %} For general instructions, supported prompts, and prompting guidelines, see [Cisco Cloud Control Canvas](https://www.cisco.com/c/en/us/td/docs/ai/cisco-cloud-control/articles/cisco-cloud-control-canvas.html). When you submit a ThousandEyes-related prompt, the request is routed to ThousandEyes with your identity and account group context. ThousandEyes then authorizes the request and generates the response from the data you are permitted to see. The account group associated with the session determines which ThousandEyes data the Cisco AI Assistant can use. ### Opting Out of GenAI-Powered Capabilities To opt out of AI functionality when using ThousandEyes with Cisco Cloud Control, you will need to opt out for both ThousandEyes and Cisco Cloud Control separately. For ThousandEyes, see [Opting Out of GenAI Capabilities](https://docs.thousandeyes.com/product-documentation/thousandeyes-and-genai#opting-out-of-genai-powered-capabilities). For Cisco Cloud Control, see [Cisco Security Cloud Control: Secure Firewall Management](https://www.cisco.com/c/en/us/td/docs/security/cdo/security_cloud_control_firewall_management/g-wrapper-firewall-administration-settings/c-tenant-settings.html). {% hint style="info" %} If you have opted out of AI capabilities in ThousandEyes and use a prompt in Cisco Cloud Control that connects to those capabilities, you will see an error message that AI features are disabled, and that an organization administrator can enable AI features in the organization settings. {% endhint %} ## Widgets ### Network Segmentation Widget The Network Segmentation widget, available in Cisco Cloud Control through AI Canvas, provides an at-a-glance view of the end-to-end network path between your monitored location and the application you are investigating. Instead of showing every network hop individually, it groups hops into meaningful network segments so you can quickly identify where a problem is occurring and which team or provider may need to investigate it. ![Network Segmentation widget showing segmented network paths in Cisco Cloud Control](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-64a7c2682f849b78e99b1c68d7a0a394ef027119%2Fnetwork-segmentation-widget-1-2.png?alt=media) {% hint style="info" %} The Network Segmentation widget complements, but does not replace, the detailed hop-by-hop [Path Visualization](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/path-visualization/). Use the Network Segmentation widget for quick triage and the path visualization for detailed investigations. {% endhint %} #### Reading the Visualization The Network Segmentation widget should be read from left to right, beginning with the agent and ending with the target server. Network hops are grouped into the following segments: | Segment | Description | | ---------------- | -------------------------------------------------------------------------------------------------------------------------- | | Agent | The ThousandEyes agent that starts the path and represents the vantage point of your site. | | Customer Network | Your internal network, including branch routers, SD-WAN, WAN interfaces, and routing to the internet edge. | | ISP | Your internet service provider's network, which is the first network outside your control. | | Internet Transit | The public internet backbone between your ISP and the target provider. | | Target Provider | The network hosting the application you are reaching, such as Microsoft, AWS, Google Cloud, or an on-premises data center. | | Target Server | The server or service that you are monitoring. | {% hint style="info" %} Overlays and underlays for SD-WAN are not supported. {% endhint %} Segments are classified automatically using the network ASN (Autonomous System Number) for each hop. You do not need to identify where one network ends and the next begins. The Network Segmentation widget displays latency on segment nodes and edges. For more information about how ThousandEyes measures and displays latency in path views, see [Comparing Latency in End-to-End Metrics and Path Visualization](https://docs.thousandeyes.com/product-documentation/tests/thousandeyes-metrics-what-do-your-results-mean#comparing-latency-in-end-to-end-metrics-vs-path-visualization). #### Viewing Behavior Over Time Network paths can change because of routing updates, failovers, and provider changes. The Network Segmentation widget shows network behavior across a selected time window rather than a single point-in-time snapshot. * The Network Segmentation widget shows an aggregate view of every path observed during the selected time window, making path changes visible in one place. * An interactive timeline, or sparkline, in the header represents the selected time window. * Hover over a path to highlight when that path was active on the timeline. * Hover over a point on the timeline to highlight all paths that were active at that time. Use the timeline to determine whether high latency occurred during a particular period, whether the path changed, when degradation began, and which segment was affected. #### Viewing Segment Details Select a segment node to open its details. The details include: * Every IP address, and the hostname when available, within the segment. * Maximum and average latency for each IP address. * A sparkline showing when each IP address was active during the selected time window. #### Identifying Providers * The **ISP** segment is labeled with your provider's name. * The **Target Provider** segment is identified by ASN, such as AWS, Azure, or Google Cloud. * The **Target Server** shows the final destination, including an IP address, hostname, or service name. #### Typical Workflow 1. In AI Canvas, the Network Segmentation widget will appear when you ask a question about the state of the network path, the path visualization of the environment, or the path from a Cloud or Enterprise Agent to a test target. 2. Scan the segments for elevated latency. 3. Use the timeline to confirm when the issue started and whether the path changed. 4. Select the affected segment to review its IP addresses and hop-level metrics. 5. Escalate to the appropriate owner based on the segment, such as your internal network operations team, ISP support, or the cloud or target provider. #### Limitations * The Network Segmentation widget supports path data from Cloud and Enterprise Agents only. * The Network Segmentation widget displays latency as its only metric. ## Troubleshooting | Issue | Troubleshooting | | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | You cannot see ThousandEyes in Cisco Cloud Control. |

Confirm that the organization is hosted in US1 or US2, uses a Cisco account, is not a managed service provider organization, and is linked to the correct tenant group. Also confirm your roles in both products.

The initial connection can take up to 12 hours for ThousandEyes to show up in Cisco Cloud Control, after the General Terms have been accepted.

| | An Enterprise Agent is missing from **Inventory**. | Confirm that the agent belongs to the linked organization and an account group that you can access. Allow time for the next inventory update. | | A ThousandEyes alert is not showing up in **Actions**. | Confirm that the alert is associated with a Network and Application Synthetics test and an account group that you can access. Batch processing can delay the update. Check the current state in ThousandEyes. | | A Cisco Cloud Control action is cleared, but the ThousandEyes alert is still active. | This behavior is expected. Clearing or dismissing the Action does not change the source alert. Manage the alert in ThousandEyes. | | An AI response does not include expected ThousandEyes data. | Confirm that the organization is linked and that you can access the relevant data in ThousandEyes. Review the supported use cases in the [Cisco Cloud Control AI Canvas](https://www.cisco.com/c/en/us/td/docs/ai/cisco-cloud-control/articles/cisco-cloud-control-canvas.html) documentation. | | When I navigate to a page in the ThousandEyes UI, the theme changes from dark mode to light mode. | Some pages in the ThousandEyes UI do not currently support dark mode. Your preferred setting will remain for pages that do support it, and light mode will be used everywhere else. |