From 0288be812066f3779906f569db3668dcbcda1b07 Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Thu, 4 Dec 2025 12:12:52 -0800 Subject: [PATCH 01/10] W-20407516 December Release --- .../pages/agent-visualizer-components.adoc | 17 +++++- .../ROOT/pages/agent-visualizer-glossary.adoc | 2 +- modules/ROOT/pages/index.adoc | 2 +- .../view-and-navigate-agent-network.adoc | 60 +++++++++++++++++++ 4 files changed, 77 insertions(+), 4 deletions(-) diff --git a/modules/ROOT/pages/agent-visualizer-components.adoc b/modules/ROOT/pages/agent-visualizer-components.adoc index 9cd3245..497adbf 100644 --- a/modules/ROOT/pages/agent-visualizer-components.adoc +++ b/modules/ROOT/pages/agent-visualizer-components.adoc @@ -26,9 +26,9 @@ For more information, see xref:view-and-navigate-agent-network.adoc#viewing-node Edges represent the relationships and communications among your nodes: * Declared edges appear between node instances when no runtime information is available because there's no registered traffic between them. Dashed lines on the graph indicate declared edges. -* Runtime edges appear between nodes when traffic is registered and a Flex Gateway exists. Solid lines on the graph indicate runtime edges. Clicking on a runtime edge opens the details card and shows the relevant metrics. +* Runtime edges appear between nodes when traffic is registered and a managed Flex Gateway exists. Solid lines on the graph indicate runtime edges. Clicking on a runtime edge opens the details card and shows the relevant metrics. + -Edges are drawn under specific conditions, primarily when the calling agent is protected by a managed Flex Gateway at egress. For more information, see xref:gateway::flex-gateway-managed-ingress-egress.adoc[]. +Edges are drawn under specific conditions, primarily when the calling agent is protected by a managed Flex Gateway at egress. For agent-to-MCP relationships, edges are automatically drawn when the calling agent’s egress or the MCP server’s ingress is protected by a managed Flex Gateway. You don't need to add new policies or extra configuration to make edges visible. For more information, see xref:gateway::flex-gateway-managed-ingress-egress.adoc[] * If an agent has an egress managed Flex Gateway, when it calls another agent, the edge is visible. * If the requesting agent doesn't have an egress Flex Gateway, no edge metric is generated and the edge isn't shown. @@ -55,6 +55,19 @@ Agent Visualizer provides a single, consistent architectural view of all assets For more information about switching between production and sandbox environment layers, see xref:view-and-navigate-agent-network.adoc#view-data-flow-layers[View Data Flow Layers]. +[[search]] +== Search + +Use the global search to find nodes in the agent network. Search is case‑insensitive and matches multiple fields: + +* Display name +* Type, for example, broker, agent, mcp +* Platform, for example, MuleSoft, Agentforce, Bedrock + +Smart suggestions show up to 10 results, ordered by relevance, with type and platform badges and an indicator of the field that matched. Selecting a result focuses the node and opens its details card. + +For more information, see xref:view-and-navigate-agent-network.adoc#search-agent-network[Search the Agent Network]. + [[details-card]] == Details Cards diff --git a/modules/ROOT/pages/agent-visualizer-glossary.adoc b/modules/ROOT/pages/agent-visualizer-glossary.adoc index c6a1b16..af8304a 100644 --- a/modules/ROOT/pages/agent-visualizer-glossary.adoc +++ b/modules/ROOT/pages/agent-visualizer-glossary.adoc @@ -25,7 +25,7 @@ For more information, see xref:anypoint-code-builder::af-define-your-agent-netwo [[declared-edge]] Declared edge:: -A design‑time relationship between two nodes (from the agent network YAML or Exchange metadata) indicating an intended connection when no runtime traffic is observed; it’s rendered as a dashed line. +A design‑time relationship between two nodes (from the agent network YAML or Exchange metadata) indicating an intended connection. When no runtime traffic is observed, it’s rendered as a dashed line. + For more information, see xref:agent-visualizer-components.adoc#edges[Edges]. diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 552cd1f..bceb05e 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -1,6 +1,6 @@ = Agent Visualizer Overview -Agent Visualizer provides a detailed visual graph so you can see, understand, and interact with your enterprise's evolving network of agents, Model Context Protocol (MCP) servers, and large language models (LLMs). Agent Visualizer gives you insight into hidden agent interactions, governance gaps, and performance bottlenecks. +Agent Visualizer provides a detailed visual graph of your agent network so you can see, understand, and interact with your enterprise's evolving network of agents, Model Context Protocol (MCP) servers, and large language models (LLMs), including agents created in external platforms like Bedrock, Gemini, Copilot, and OpenAI. Agent Visualizer gives you insight into hidden agent interactions, governance gaps, and performance bottlenecks. Agent Visualizer is an intuitive user interface that helps you: diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index 7fe271d..9169de0 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -55,6 +55,66 @@ When you select an edge, the details card displays relationship information and . Select an edge to open its details card. . Examine the traffic throughput per hour. +[[view-external-nodes]] +== View External Agents and MCP Servers + +External agents and MCP servers appear as nodes in the agent network. You can select these nodes to view metadata and, when available, instance details. + +. Select an external agent or MCP server node to open its details card and review the node’s metadata. ++ +If runtime edges aren't visible for calls involving external agents: ++ +.. Add telemetry by protecting the relevant path with a managed Flex Gateway. +.. Inject identifying headers needed for visualization (for example, source and destination identifiers). +.. Generate traffic and refresh the view to draw the runtime edge. ++ +[NOTE] +Depending on your configuration, edges between external agents may not draw automatically until the gateway protection and header injection are in place and traffic is observed. + +[[view-mcp-server-edges-tools]] +== View MCP Server Edges and Tools + +When agents invoke MCP servers, Agent Visualizer shows the relationship on the graph and tool usage on the MCP node’s details card. + +. Select an MCP server node to focus associated edges and open its details card. ++ +Tool invocations from multiple agents are aggregated into a single list on the MCP server: ++ +** Tools are ordered by throughput (total MCP calls). +** The top 10 tools are shown by default. ++ +Click *Show More* to see additional tools when available. ++ +[NOTE] +For tool visibility, the MCP server must be present in Exchange and the egress path must be protected by a managed Flex Gateway. This applies to MuleSoft‑hosted MCP servers defined in the broker network and externally hosted MCP servers defined in the broker network. ++ +. To see traffic metrics on the connection, select the edge between the agent and the MCP server and open the edge details card. + +[[view-standalone-agents]] +== View Agents without Flex Gateway + +Agents that aren't protected by a managed Flex Gateway appear as standalone nodes with declared edges only. You can still view their metadata and understand their purpose in the network. + +. Select the agent node to open its details card. ++ +Review metadata, tags, and any instance details available. +. To visualize runtime edges and performance metrics, protect the agent with a managed Flex Gateway on the relevant path (ingress or egress), then generate traffic. + +[[search-agent-network]] +== Search the Agent Network + +Use search to locate nodes in the agent network. Search is case‑insensitive and supports multiple fields: + +* Display name +* Type, for example, broker, agent, MCP +* Platform, for example, MuleSoft, Agentforce, Bedrock + +. Select the search box and enter a name, type, or platform. ++ +Up to 10 results are shown, ordered by relevance. Each result displays a type badge and a platform badge, along with an indicator of which field matched. ++ +Search results reflect the current base graph. Environment layer selection (Production or Sandbox) affects instance‑level metrics but not which nodes can be found by search. + == See Also * xref:index.adoc[] From 8d29ddf9102235e11a2c9ec0cc1a2899837adc47 Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Thu, 4 Dec 2025 12:36:49 -0800 Subject: [PATCH 02/10] Added Filter --- .../pages/agent-visualizer-components.adoc | 14 ------ .../view-and-navigate-agent-network.adoc | 46 +++++++++++++++++-- 2 files changed, 41 insertions(+), 19 deletions(-) diff --git a/modules/ROOT/pages/agent-visualizer-components.adoc b/modules/ROOT/pages/agent-visualizer-components.adoc index 497adbf..23e70b5 100644 --- a/modules/ROOT/pages/agent-visualizer-components.adoc +++ b/modules/ROOT/pages/agent-visualizer-components.adoc @@ -54,20 +54,6 @@ Agent Visualizer provides a single, consistent architectural view of all assets For more information about switching between production and sandbox environment layers, see xref:view-and-navigate-agent-network.adoc#view-data-flow-layers[View Data Flow Layers]. - -[[search]] -== Search - -Use the global search to find nodes in the agent network. Search is case‑insensitive and matches multiple fields: - -* Display name -* Type, for example, broker, agent, mcp -* Platform, for example, MuleSoft, Agentforce, Bedrock - -Smart suggestions show up to 10 results, ordered by relevance, with type and platform badges and an indicator of the field that matched. Selecting a result focuses the node and opens its details card. - -For more information, see xref:view-and-navigate-agent-network.adoc#search-agent-network[Search the Agent Network]. - [[details-card]] == Details Cards diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index 9169de0..4ec462a 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -103,18 +103,54 @@ Review metadata, tags, and any instance details available. [[search-agent-network]] == Search the Agent Network -Use search to locate nodes in the agent network. Search is case‑insensitive and supports multiple fields: +Use search to locate nodes in the agent network. Search is case‑insensitive and supports multiple fields. -* Display name +. Select the search box and enter your search terms. ++ +You can search by: ++ +* Display name * Type, for example, broker, agent, MCP -* Platform, for example, MuleSoft, Agentforce, Bedrock - -. Select the search box and enter a name, type, or platform. +* Platform, for example, MuleSoft, Agentforce, Bedrock +* Exchange tags ++ +Smart suggestions show up to 10 results, ordered by relevance, with type and platform badges and an indicator of the field that matched. Selecting a result focuses the node and opens its details card. + Up to 10 results are shown, ordered by relevance. Each result displays a type badge and a platform badge, along with an indicator of which field matched. + Search results reflect the current base graph. Environment layer selection (Production or Sandbox) affects instance‑level metrics but not which nodes can be found by search. +== Add Filters + +Use filters to control which parts of the network you see on the canvas. Filters help you focus large graphs by limiting the scope to specific business groups and time windows. + +[[filter-business-groups]] +=== Select Business Groups + +Select one or more business groups to include their assets and relationships in a single, unified view. + +. Open the filter panel and select the Business Group filter. +. Select one or more business groups to include. + + + By default, your current business group is selected. Only business groups for which you have Agent Visualizer permissions appear in the list. ++ +The agent network graph shows assets that belong to the selected business groups, and edges between those assets (including cross‑business group connections) are shown on the same map. ++ +Metrics on nodes and edges are aggregated based on the business groups you select. When you deselect business groups, metrics update to reflect only the remaining selection. ++ +[TIP] +The agent network graph shows which business groups are in scope (for example, in the filter panel or as badges). If performance degrades when viewing many business groups at once, reduce the selection, use search, or zoom to areas of interest. + +[[filter-time-range]] +=== Select a Time Range + +Adjust the time window to control which runtime edges and metrics are shown. + +. Open the filter panel and choose a time range. +The agent network graph shows runtime edges that reflect traffic observed within the selected window; declared edges are unaffected. Throughput, error rates, and tool rankings also reflect the selected time range. ++ +Change the time range as needed to compare recent activity (for example, last hour) with broader trends (for example, last 3 or 7 days). + == See Also * xref:index.adoc[] From b2324c28e4c2e19694d33e702c1a9d70074a0a82 Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Thu, 4 Dec 2025 13:03:55 -0800 Subject: [PATCH 03/10] Edits --- .../view-and-navigate-agent-network.adoc | 38 +++++++++++++------ 1 file changed, 27 insertions(+), 11 deletions(-) diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index 4ec462a..0e0909e 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -122,24 +122,40 @@ Search results reflect the current base graph. Environment layer selection (Prod == Add Filters -Use filters to control which parts of the network you see on the canvas. Filters help you focus large graphs by limiting the scope to specific business groups and time windows. +Use filters to control which parts of the network you see on the canvas. Filters help you focus large graphs by limiting the scope to specific business groups and time windows. -[[filter-business-groups]] -=== Select Business Groups +The agent network graph shows assets that belong to the selected business groups, and edges between those assets (including cross‑business group connections) are shown on the same map. + +Metrics on nodes and edges are aggregated based on the business groups you select. When you deselect business groups, metrics update to reflect only the remaining selection. -Select one or more business groups to include their assets and relationships in a single, unified view. +[[filter-business-groups]] +=== Apply Filters to the Agent Network -. Open the filter panel and select the Business Group filter. -. Select one or more business groups to include. - + - By default, your current business group is selected. Only business groups for which you have Agent Visualizer permissions appear in the list. +. Open the filter panel and select the filters to apply: + -The agent network graph shows assets that belong to the selected business groups, and edges between those assets (including cross‑business group connections) are shown on the same map. +* *Business Groups* + -Metrics on nodes and edges are aggregated based on the business groups you select. When you deselect business groups, metrics update to reflect only the remaining selection. +By default, your current business group is selected. Only business groups you have Agent Visualizer permissions for appear in the list. ++ +Select one or more business groups. + [TIP] -The agent network graph shows which business groups are in scope (for example, in the filter panel or as badges). If performance degrades when viewing many business groups at once, reduce the selection, use search, or zoom to areas of interest. +If performance degrades when viewing many business groups at once, reduce the selection, use search, or zoom to areas of interest. +* *Environment* ++ +Select *Production* or *Sandbox*. +* *Activity Period* ++ +Select the last: +** *24 hours* +** *3 days* +** *5 days* +** *7 days* +* *Display Options* ++ +You can hide standalone nodes and edges. +. Click *Apply Filters*. + [[filter-time-range]] === Select a Time Range From 7f6b0a92ad7d6b6f3f56dfe8fe1a2fc1aaaf5fb3 Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Fri, 5 Dec 2025 08:10:22 -0800 Subject: [PATCH 04/10] Edits --- .../view-and-navigate-agent-network.adoc | 39 +++++++------------ 1 file changed, 14 insertions(+), 25 deletions(-) diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index 0e0909e..500784a 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -58,23 +58,20 @@ When you select an edge, the details card displays relationship information and [[view-external-nodes]] == View External Agents and MCP Servers -External agents and MCP servers appear as nodes in the agent network. You can select these nodes to view metadata and, when available, instance details. +External agents and MCP servers that are published to Exchange appear as nodes in the agent network. You can select these nodes to view metadata and, when available, instance details. . Select an external agent or MCP server node to open its details card and review the node’s metadata. + -If runtime edges aren't visible for calls involving external agents: -+ -.. Add telemetry by protecting the relevant path with a managed Flex Gateway. -.. Inject identifying headers needed for visualization (for example, source and destination identifiers). -.. Generate traffic and refresh the view to draw the runtime edge. -+ [NOTE] -Depending on your configuration, edges between external agents may not draw automatically until the gateway protection and header injection are in place and traffic is observed. +==== +If runtime edges aren't visible for calls involving external agents, add telemetry by protecting the relevant path with a managed Flex Gateway and inject identifying headers needed for visualization (for example, source and destination identifiers). +Then, generate traffic and refresh the view to draw the runtime edge. +==== [[view-mcp-server-edges-tools]] == View MCP Server Edges and Tools -When agents invoke MCP servers, Agent Visualizer shows the relationship on the graph and tool usage on the MCP node’s details card. +When agents invoke MCP servers, Agent Visualizer shows the relationship on the graph and lists MCP tools on the MCP server node’s details card. . Select an MCP server node to focus associated edges and open its details card. + @@ -88,6 +85,8 @@ Click *Show More* to see additional tools when available. [NOTE] For tool visibility, the MCP server must be present in Exchange and the egress path must be protected by a managed Flex Gateway. This applies to MuleSoft‑hosted MCP servers defined in the broker network and externally hosted MCP servers defined in the broker network. + +The tools list reflects the selected activity period and shows only tools that were invoked during that window. Allowlisted tools that aren't called don't appear. If the MCP server exposes a tool catalog that Agent Visualizer can query, the details panel shows the full set of available (design‑time) tools alongside runtime usage. ++ . To see traffic metrics on the connection, select the edge between the agent and the MCP server and open the edge details card. [[view-standalone-agents]] @@ -103,7 +102,7 @@ Review metadata, tags, and any instance details available. [[search-agent-network]] == Search the Agent Network -Use search to locate nodes in the agent network. Search is case‑insensitive and supports multiple fields. +Use search to locate nodes in the agent network. Search is case‑insensitive and supports multiple fields. Search results reflect the current base graph. Environment layer selection (Production or Sandbox) affects instance‑level metrics but not which nodes can be found by search. . Select the search box and enter your search terms. + @@ -114,15 +113,16 @@ You can search by: * Platform, for example, MuleSoft, Agentforce, Bedrock * Exchange tags + -Smart suggestions show up to 10 results, ordered by relevance, with type and platform badges and an indicator of the field that matched. Selecting a result focuses the node and opens its details card. +Smart suggestions show up to 10 results, ordered by relevance, with type and platform badges and an indicator of the field that matched. + -Up to 10 results are shown, ordered by relevance. Each result displays a type badge and a platform badge, along with an indicator of which field matched. +Up to 10 results are shown, ordered by relevance. Each result shows a type badge and a platform badge, along with an indicator of the matched field. + -Search results reflect the current base graph. Environment layer selection (Production or Sandbox) affects instance‑level metrics but not which nodes can be found by search. +. Select a result to zoom in on the node and open its details card. + == Add Filters -Use filters to control which parts of the network you see on the canvas. Filters help you focus large graphs by limiting the scope to specific business groups and time windows. +Use filters to control which parts of the network you see on the canvas. Filters help you focus on the information you need in large graphs by limiting the scope to specific business groups and time windows. The agent network graph shows assets that belong to the selected business groups, and edges between those assets (including cross‑business group connections) are shown on the same map. @@ -156,17 +156,6 @@ Select the last: You can hide standalone nodes and edges. . Click *Apply Filters*. - -[[filter-time-range]] -=== Select a Time Range - -Adjust the time window to control which runtime edges and metrics are shown. - -. Open the filter panel and choose a time range. -The agent network graph shows runtime edges that reflect traffic observed within the selected window; declared edges are unaffected. Throughput, error rates, and tool rankings also reflect the selected time range. -+ -Change the time range as needed to compare recent activity (for example, last hour) with broader trends (for example, last 3 or 7 days). - == See Also * xref:index.adoc[] From df1c134c20f8852f9502d35d8a3e5b860149b467 Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Tue, 9 Dec 2025 08:50:12 -0800 Subject: [PATCH 05/10] Added tool details --- .../pages/agent-visualizer-components.adoc | 23 ++++++++++++++++++- modules/ROOT/pages/index.adoc | 2 +- 2 files changed, 23 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/agent-visualizer-components.adoc b/modules/ROOT/pages/agent-visualizer-components.adoc index 23e70b5..428b280 100644 --- a/modules/ROOT/pages/agent-visualizer-components.adoc +++ b/modules/ROOT/pages/agent-visualizer-components.adoc @@ -65,7 +65,7 @@ For more information, see xref:view-and-navigate-agent-network.adoc#view-node-de === Node Metadata -When you select a node, the details card shows metadata for that asset, including: +When you select a node, the details card shows metadata for that agentic asset, including: [%header,cols="30a,70a"] |=== @@ -122,6 +122,27 @@ Each instance entry includes the asset version number, so you can easily disting + Instances are ordered from the most recent (latest) to least recent (earliest) asset version, making it easy to track version history over time. +=== MCP Server Details + +The MCP server details card includes active MCP tools and per‑instance activity: + +* Active tools reflect the selected Activity Period and only include tools invoked during that window. +* Tools are aggregated across all instances of the MCP server, ranked by throughput, with the top 10 displayed by default. Select *Show More* to view additional tools. + +[NOTE] +Tool visibility requires the MCP asset to be published in Exchange and telemetry from a managed Flex Gateway on the relevant path. Allowlisted tools that haven't been called don't appear in runtime usage. + +=== Tool Details + +When you select a tool, the tool details card opens. It shows: + +* Tool name, icon, and MCP asset information at the top +* Active instances count (instances with traffic for this tool) +* A list of instances with per‑instance metrics (total calls and error rate) for the selected tool + +If more than two instances are shown, a scroller is enabled. Long tool names are truncated with an ellipsis. + + [[policy-visualization]] == Policy Visualization diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index bceb05e..f82f797 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -1,6 +1,6 @@ = Agent Visualizer Overview -Agent Visualizer provides a detailed visual graph of your agent network so you can see, understand, and interact with your enterprise's evolving network of agents, Model Context Protocol (MCP) servers, and large language models (LLMs), including agents created in external platforms like Bedrock, Gemini, Copilot, and OpenAI. Agent Visualizer gives you insight into hidden agent interactions, governance gaps, and performance bottlenecks. +Agent Visualizer provides a detailed visual graph of your agent network so you can see, understand, and interact with your enterprise's evolving network of agents, Model Context Protocol (MCP) servers, and large language models (LLMs), including agents created in external platforms like Bedrock, Copilot, and Vertex AI. Agent Visualizer gives you insight into hidden agent interactions, governance gaps, and performance bottlenecks. Agent Visualizer is an intuitive user interface that helps you: From 1b25e23c574f060041ac67fb3f1504a4c558378c Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Tue, 9 Dec 2025 09:15:11 -0800 Subject: [PATCH 06/10] Edits --- modules/ROOT/pages/agent-visualizer-components.adoc | 11 ++++------- .../ROOT/pages/view-and-navigate-agent-network.adoc | 3 +-- 2 files changed, 5 insertions(+), 9 deletions(-) diff --git a/modules/ROOT/pages/agent-visualizer-components.adoc b/modules/ROOT/pages/agent-visualizer-components.adoc index 428b280..b7e18f3 100644 --- a/modules/ROOT/pages/agent-visualizer-components.adoc +++ b/modules/ROOT/pages/agent-visualizer-components.adoc @@ -130,18 +130,15 @@ The MCP server details card includes active MCP tools and per‑instance activit * Tools are aggregated across all instances of the MCP server, ranked by throughput, with the top 10 displayed by default. Select *Show More* to view additional tools. [NOTE] -Tool visibility requires the MCP asset to be published in Exchange and telemetry from a managed Flex Gateway on the relevant path. Allowlisted tools that haven't been called don't appear in runtime usage. +Tool visibility requires the MCP asset to be published in Exchange and telemetry from a managed Flex Gateway on the relevant path. Runtime usage shows only allowlisted tools that have been called. === Tool Details When you select a tool, the tool details card opens. It shows: -* Tool name, icon, and MCP asset information at the top -* Active instances count (instances with traffic for this tool) -* A list of instances with per‑instance metrics (total calls and error rate) for the selected tool - -If more than two instances are shown, a scroller is enabled. Long tool names are truncated with an ellipsis. - +* Tool name, icon, and MCP asset information at the top. +* Active instances count (instances with traffic for this tool). If more than two instances are shown, a scrollbar is enabled. +* A list of instances with per‑instance metrics (total calls and error rate) for the selected tool. [[policy-visualization]] == Policy Visualization diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index 500784a..481a0b0 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -115,11 +115,10 @@ You can search by: + Smart suggestions show up to 10 results, ordered by relevance, with type and platform badges and an indicator of the field that matched. + -Up to 10 results are shown, ordered by relevance. Each result shows a type badge and a platform badge, along with an indicator of the matched field. +Each result shows a type badge and a platform badge, along with an indicator of the matched field. + . Select a result to zoom in on the node and open its details card. - == Add Filters Use filters to control which parts of the network you see on the canvas. Filters help you focus on the information you need in large graphs by limiting the scope to specific business groups and time windows. From 8b5518e63f6e578948c12c6c246504dccf920169 Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Tue, 9 Dec 2025 09:36:43 -0800 Subject: [PATCH 07/10] Update view-and-navigate-agent-network.adoc --- .../ROOT/pages/view-and-navigate-agent-network.adoc | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index 481a0b0..9a73990 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -104,7 +104,17 @@ Review metadata, tags, and any instance details available. Use search to locate nodes in the agent network. Search is case‑insensitive and supports multiple fields. Search results reflect the current base graph. Environment layer selection (Production or Sandbox) affects instance‑level metrics but not which nodes can be found by search. -. Select the search box and enter your search terms. +. Open the search box. ++ +.Show me how +[%collapsible] +==== +* Click the magnifying glass icon. +* Use the keyboard shortcuts: +** Mac: Cmd+Shift+k +** Windows: Ctrl+Shift+k +==== +. Enter your search terms. + You can search by: + From 090cc64c935b257b8d1c2ed2e2b89945e40273cf Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Tue, 9 Dec 2025 09:40:29 -0800 Subject: [PATCH 08/10] Update view-and-navigate-agent-network.adoc --- modules/ROOT/pages/view-and-navigate-agent-network.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index 9a73990..c2b57ad 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -128,6 +128,7 @@ Smart suggestions show up to 10 results, ordered by relevance, with type and pla Each result shows a type badge and a platform badge, along with an indicator of the matched field. + . Select a result to zoom in on the node and open its details card. +. Press the escape key to clear the results and close the search box. == Add Filters From 44f7bb8cbee5fe571efd295af45055f35a2f0545 Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Thu, 15 Jan 2026 10:21:25 -0800 Subject: [PATCH 09/10] Adding example --- modules/ROOT/pages/index.adoc | 2 +- .../view-and-navigate-agent-network.adoc | 59 ++++++++++++++----- 2 files changed, 46 insertions(+), 15 deletions(-) diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index f82f797..27ddc60 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -6,7 +6,7 @@ Agent Visualizer provides a detailed visual graph of your agent network so you c Agent Visualizer is an intuitive user interface that helps you: * Gain complete situational awareness of your agentic ecosystem with a view of all connected agents in your agent network on one map, including clear relationships and direction of calls. -* See unclear interaction patterns by showing real-time call volume for the past 24 hours. This helps you understand key pathways and identify under- or overused connections. +* See unclear interaction patterns by showing real-time call volume. This helps you understand key pathways and identify under- or overused connections. * See governance gaps with a view of which agents are protected by Flex Gateways and policies. * Understand node purpose and origin. + diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index c2b57ad..6f94914 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -62,11 +62,7 @@ External agents and MCP servers that are published to Exchange appear as nodes i . Select an external agent or MCP server node to open its details card and review the node’s metadata. + -[NOTE] -==== -If runtime edges aren't visible for calls involving external agents, add telemetry by protecting the relevant path with a managed Flex Gateway and inject identifying headers needed for visualization (for example, source and destination identifiers). -Then, generate traffic and refresh the view to draw the runtime edge. -==== +To visualize runtime edges for external agents, see xref:view-standalone-agents[View Agents Without Flex Gateway]. [[view-mcp-server-edges-tools]] == View MCP Server Edges and Tools @@ -89,10 +85,48 @@ The tools list reflects the selected activity period and shows only tools that w + . To see traffic metrics on the connection, select the edge between the agent and the MCP server and open the edge details card. +=== Example: Visualize Interactions Between External Agents and MCP Servers + +To visualize runtime edges for external agents and MCP servers that aren't part of a defined agent network, you must manually register them as API assets and route their traffic through Flex Gateway. + +This is an example of how to visualize the interactions between agents and MCP servers when they aren’t part of an agent network. This process manually "onboards" your external assets so they appear in the agent network graph as managed nodes with live traffic edges. + +. Publish your external MCP servers to Anypoint Exchange as API assets. +. Setup a Flex Gateway in Connected Mode. ++ +This gateway acts as the "exit point" that intercepts calls going to the external servers. +. In API Manager, create a new instance for each external MCP server. +.. Point the Implementation URI to the actual external URL of your MCP server. +.. Deploy these instances to your Egress Flex Gateway. +. Enable telemetry by injecting identifying headers for visualization (for example, source and destination identifiers): +.. In API Manager, go to the *Policies* tab for these instances. +.. Apply the Agent Connection Telemetry policy. This allows the gateway to parse MCP-specific traffic (like list tools). +.. Record the Consumer URL (the Flex Gateway endpoint) for each MCP server. +. Publish the agent asset in Anypoint Exchange with the *Agent* type. +. Setup the Ingress Flex Gateway to handle the inbound traffic to the agent. +. In API Manager, go to *Agent and Tools Instances* and select *Add > Agent*. +.. Assign the agent to the Ingress Flex Gateway. +.. Copy the Agent Instance ID. ++ +The external agent uses this ID to identify itself to the Ingress Flex Gateway. +. In API Manager, apply a *Header Injection* policy to the agent instance. +.. Add the *Header Name* as `x-agent-instance-id` and the *Header Value* as the Agent Instance ID you copied earlier. +.. Click *Apply*. +. On the calling agent app, inject the `x-anypoint-api-instance-id` header (on list tools or call tools operations) providing the agent Instance ID from the ingress entry in API Manager as the value of the header. + + + + + + + + + + [[view-standalone-agents]] -== View Agents without Flex Gateway +== View Agents Without Flex Gateway -Agents that aren't protected by a managed Flex Gateway appear as standalone nodes with declared edges only. You can still view their metadata and understand their purpose in the network. +Agents that aren't protected by a managed Flex Gateway appear as standalone nodes. You can still view their metadata and understand their purpose in the network. . Select the agent node to open its details card. + @@ -123,10 +157,7 @@ You can search by: * Platform, for example, MuleSoft, Agentforce, Bedrock * Exchange tags + -Smart suggestions show up to 10 results, ordered by relevance, with type and platform badges and an indicator of the field that matched. -+ -Each result shows a type badge and a platform badge, along with an indicator of the matched field. -+ +Smart suggestions show up to 10 results, ordered by relevance, with type and platform badges and an indicator of the matched field. . Select a result to zoom in on the node and open its details card. . Press the escape key to clear the results and close the search box. @@ -145,12 +176,12 @@ Metrics on nodes and edges are aggregated based on the business groups you selec + * *Business Groups* + -By default, your current business group is selected. Only business groups you have Agent Visualizer permissions for appear in the list. +By default, your current business group is selected. You can select multiple business groups to see cross-business group connections in a single view. Only business groups you have Agent Visualizer permissions for appear in the list. + -Select one or more business groups. +When multiple business groups are selected, the canvas shows assets belonging to the selected business groups and edges between those assets across all selected business groups. The metrics that are shown are aggregated across all selected business groups. When you deselect business groups, metrics update to reflect only the remaining selection. + [TIP] -If performance degrades when viewing many business groups at once, reduce the selection, use search, or zoom to areas of interest. +If performance degrades when viewing multiple business groups at once, reduce the selection, use search, or zoom to areas of interest. * *Environment* + Select *Production* or *Sandbox*. From 4ac268de0da15a17cd52db5c259badcc30584111 Mon Sep 17 00:00:00 2001 From: valkyrie69 Date: Thu, 15 Jan 2026 11:22:25 -0800 Subject: [PATCH 10/10] Adding xrefs --- .../view-and-navigate-agent-network.adoc | 21 +++++++------------ 1 file changed, 8 insertions(+), 13 deletions(-) diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index 6f94914..b509fd9 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -12,7 +12,7 @@ include::partial$partial-agent-visualizer.adoc[tag=agent-visualizer-permissions] + On the Agent Visualizer page, you see the agent network map showing all discovered agentic assets, nodes and their relationships (edges). -If the page is empty, there are no discoverable agentic assets in Anypoint Exchange. For more information about creating an agent network project and publishing assets to Exchange, see xref:anypoint-code-builder::af-create-agent-network.adoc[]. +If the page is empty, there are no discoverable agentic assets in Anypoint Exchange (Exchange). For more information about creating an agent network project and publishing assets to Exchange, see xref:anypoint-code-builder::af-create-agent-network.adoc[]. [[navigate-agent-network]] == Navigate the Agent Network @@ -87,14 +87,18 @@ The tools list reflects the selected activity period and shows only tools that w === Example: Visualize Interactions Between External Agents and MCP Servers -To visualize runtime edges for external agents and MCP servers that aren't part of a defined agent network, you must manually register them as API assets and route their traffic through Flex Gateway. +To visualize runtime edges for external agents and MCP servers that aren't part of a defined agent network, you must publish them to Anypoint Exchange and route their traffic through Flex Gateway. This is an example of how to visualize the interactions between agents and MCP servers when they aren’t part of an agent network. This process manually "onboards" your external assets so they appear in the agent network graph as managed nodes with live traffic edges. -. Publish your external MCP servers to Anypoint Exchange as API assets. -. Setup a Flex Gateway in Connected Mode. +. Publish your MCP servers to Anypoint Exchange. ++ +For more information about creating assets in Exchange, see xref:exchange::to-create-an-asset.adoc#create-mcp[]. +. Set up a Flex Gateway in Connected Mode. + This gateway acts as the "exit point" that intercepts calls going to the external servers. ++ +For more information about securing agent interaction in Flex Gateway, see xref:gateway::flex-agent-secure.adoc[]. . In API Manager, create a new instance for each external MCP server. .. Point the Implementation URI to the actual external URL of your MCP server. .. Deploy these instances to your Egress Flex Gateway. @@ -114,15 +118,6 @@ The external agent uses this ID to identify itself to the Ingress Flex Gateway. .. Click *Apply*. . On the calling agent app, inject the `x-anypoint-api-instance-id` header (on list tools or call tools operations) providing the agent Instance ID from the ingress entry in API Manager as the value of the header. - - - - - - - - - [[view-standalone-agents]] == View Agents Without Flex Gateway