diff --git a/modules/ROOT/pages/agent-visualizer-components.adoc b/modules/ROOT/pages/agent-visualizer-components.adoc index b5a84b9..8d248a4 100644 --- a/modules/ROOT/pages/agent-visualizer-components.adoc +++ b/modules/ROOT/pages/agent-visualizer-components.adoc @@ -6,7 +6,7 @@ Use Agent Visualizer to identify the parts of your agent network and see how the * View edges to see declared and runtime interactions. * Use layers to focus views on specific environments * Open details cards to inspect metadata and metrics for nodes and access logs and traces -* Review governance indicators such as Flex Gateway protection and applied policies. +* Review governance indicators such as Omni Gateway protection and applied policies. [[node-types]] == Node Types @@ -28,13 +28,13 @@ include::partial$partial-agent-visualizer.adoc[tag=node-limit-note] 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 managed Flex Gateway exists. Solid lines on the graph indicate runtime edges. Click a runtime edge to open the details card and show the relevant metrics. +* Runtime edges appear between nodes when traffic is registered and a managed Omni Gateway exists. Solid lines on the graph indicate runtime edges. Click a runtime edge to open the details card and show the relevant metrics. + -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[] +Edges are drawn under specific conditions, primarily when the calling agent is protected by a managed Omni 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 Omni 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. -* Broker agents that route outbound calls through an egress Flex Gateway, allowing requests between broker agents, or from a broker agent to an external agent, appear in the agent network visualization. +* If an agent has an egress managed Omni Gateway, when it calls another agent, the edge is visible. +* If the requesting agent doesn't have an egress Omni Gateway, no edge metric is generated and the edge isn't shown. +* Broker agents that route outbound calls through an egress Omni Gateway, allowing requests between broker agents, or from a broker agent to an external agent, appear in the agent network visualization. Selecting an edge opens the details card, which displays relationship information and metrics. For more information, see xref:view-and-navigate-agent-network.adoc#view-edge-details[View Edge Details]. @@ -46,7 +46,7 @@ Agent Visualizer provides a single, consistent architectural view of all assets * Base graph ** Always visible ** Shows all assets defined in Exchange (agents and MCP servers) and their design‑time relationships from broker definitions -** Topology and layout do not change when switching layers +** Topology and layout don't change when switching layers * Production layer ** Overlays production instances and metrics on existing nodes and edges ** Hides sandbox traffic lines @@ -85,7 +85,7 @@ When you select a node, the details card shows metadata for that agentic asset, | Environment Type | Environments the instance is deployed to, for example, `sandbox` or `production`. | Based on Asset Version | Version of the instance. | Policies | Policies that are applied to the instance. -| Governance and Security | Whether the asset is protected by a Flex Gateway. +| Governance and Security | Whether the asset is protected by an Omni Gateway. | Performance and Health a| Performance and health metrics for the instance including: * Successful Requests @@ -132,7 +132,7 @@ 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] -You need to publish MCP assets in Exchange before the tools are visible. Tools also require telemetry from a managed Flex Gateway on the relevant path. Runtime usage shows only allowlisted tools that have been called. +You need to publish MCP assets in Exchange before the tools are visible. Tools also require telemetry from a managed Omni Gateway on the relevant path. Runtime usage shows only allowlisted tools that have been called. === Tool Details @@ -145,7 +145,7 @@ When you select a tool, the tool details card opens. It shows: [[policy-visualization]] == Policy Visualization -The policy visualization shows nodes that are protected by a Flex Gateway indicated by a shield icon. Data about applied policies comes from API Manager. +The policy visualization shows nodes that are protected by an Omni Gateway indicated by a shield icon. Data about applied policies comes from API Manager. You can see the details of applied policies in the details card for the selected node. diff --git a/modules/ROOT/pages/agent-visualizer-glossary.adoc b/modules/ROOT/pages/agent-visualizer-glossary.adoc index af8304a..6aeee4d 100644 --- a/modules/ROOT/pages/agent-visualizer-glossary.adoc +++ b/modules/ROOT/pages/agent-visualizer-glossary.adoc @@ -30,10 +30,10 @@ A design‑time relationship between two nodes (from the agent network YAML or E For more information, see xref:agent-visualizer-components.adoc#edges[Edges]. [[managed-flex-gateway]] -Managed Flex Gateway:: -A Flex Gateway that is managed by Anypoint Platform. +Managed Omni Gateway:: +An Omni Gateway that is managed by Anypoint Platform. + -For more information, see xref:gateway::index.adoc#managed[Managed Flex Gateway]. +For more information, see xref:gateway::index.adoc#managed[Managed Omni Gateway]. [[mcp-server]] MCP Server:: @@ -41,7 +41,7 @@ A service that implements the Model Context Protocol (MCP) to expose tools and d [[runtime-edge]] Runtime edge:: -A live relationship that's drawn when actual traffic is observed between two nodes (from Flex Gateway or Monitoring telemetry). It’s rendered as a solid line in the agent network. +A live relationship that's drawn when actual traffic is observed between two nodes (from Omni Gateway or Monitoring telemetry). It’s rendered as a solid line in the agent network. + 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 1fb05ee..3f49d62 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -7,7 +7,7 @@ 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. 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. +* See governance gaps with a view of which agents are protected by Omni Gateways and policies. * Understand node purpose and origin. + You gain full understanding of each asset in your agent network and any active running instances when you select a node. diff --git a/modules/ROOT/pages/node-governance.adoc b/modules/ROOT/pages/node-governance.adoc index e2fb0f5..c9a346b 100644 --- a/modules/ROOT/pages/node-governance.adoc +++ b/modules/ROOT/pages/node-governance.adoc @@ -1,26 +1,26 @@ = Governing Nodes -See which nodes in your agent network are protected and which policies are applied. Open the asset in API Manager to review more details about its policies. If a node isn’t protected, you can add a managed Flex Gateway and create the appropriate instance to enforce policies. +See which nodes in your agent network are protected and which policies are applied. Open the asset in API Manager to review more details about its policies. If a node isn’t protected, you can add a managed Omni Gateway and create the appropriate instance to enforce policies. [[view-node-policies]] == View Node Policies -. Look for the shield icon on nodes to see which nodes are secured by Flex Gateways. +. Look for the shield icon on nodes to see which nodes are secured by Omni Gateways. . Click the node to open the details card and see the policies that are applied to the node. . Click *View Policies* to view the policies for this instance in API Manager. + Policies are listed by category on the left and applied policies are listed on the right. [[add-a-flex-gateway]] -== Add a Flex Gateway +== Add an Omni Gateway -Add a managed Flex Gateway to the node to enforce authentication, rate limits, and other policies at ingress and egress, and to emit telemetry for monitoring and visualization. +Add a managed Omni Gateway to the node to enforce authentication, rate limits, and other policies at ingress and egress, and to emit telemetry for monitoring and visualization. . Click the node to open the details card. . Click *Add Flex Gateway*. . In API Manager, add an instance of the asset (MCP server or agent) to protect. + -For information about adding an MCP server or agent instance, see xref:api-manager::create-instance-task-agent-tool.adoc[Add a Flex Gateway Agent or Tool Instance]. +For information about adding an MCP server or agent instance, see xref:api-manager::create-instance-task-agent-tool.adoc[Add an Omni Gateway Agent or Tool Instance]. == See Also diff --git a/modules/ROOT/pages/view-and-navigate-agent-network.adoc b/modules/ROOT/pages/view-and-navigate-agent-network.adoc index 0f42421..aaac93a 100644 --- a/modules/ROOT/pages/view-and-navigate-agent-network.adoc +++ b/modules/ROOT/pages/view-and-navigate-agent-network.adoc @@ -67,7 +67,7 @@ External agents and MCP servers that are published to Exchange appear as nodes i . To open its details card and review the node’s metadata, select an external agent or MCP server node. + [NOTE] -To visualize runtime edges for external agents, see <>. +To visualize runtime edges for external agents, see <>. [[view-mcp-server-edges-tools]] == View MCP Server Edges and Tools @@ -84,7 +84,7 @@ Tool invocations from multiple agents are aggregated into a single list on the M 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. +For tool visibility, the MCP server must be present in Exchange and the egress path must be protected by a managed Omni 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. + @@ -92,46 +92,46 @@ 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 publish them to Anypoint Exchange as agents or tools 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 as agents or tools and route their traffic through Omni Gateway. This example shows 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 agents and 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. +. Set up an Omni Gateway in Connected Mode. + -To enable visualization, both the calling agents and the MCP servers must be governed by Flex Gateway. By routing traffic through a gateway endpoint instead of calling the server directly, the gateway intercepts the request, injects identity headers, and reports the interaction to the Agent Visualizer. +To enable visualization, both the calling agents and the MCP servers must be governed by Omni Gateway. By routing traffic through a gateway endpoint instead of calling the server directly, the gateway intercepts the request, injects identity headers, and reports the interaction to the Agent Visualizer. + -For more information about securing agent interaction in Flex Gateway, see xref:gateway::flex-agent-secure.adoc[]. +For more information about securing agent interaction in Omni Gateway, see xref:gateway::flex-agent-secure.adoc[]. . In API Manager, create a new instance for each MCP server. .. Point the Implementation URI to the actual external URL of your MCP server. -.. Deploy these instances to your egress Flex Gateway. +.. Deploy these instances to your egress Omni 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. +.. Record the Consumer URL (the Omni Gateway endpoint) for each MCP server. . Publish the agent asset in Anypoint Exchange with the *Agent* type. -. Set up the ingress Flex Gateway to handle the inbound traffic to the agent. +. Set up the ingress Omni 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. +.. Assign the agent to the Ingress Omni Gateway. .. Copy the Agent Instance ID. + -The external agent uses this ID to identify itself to the Ingress Flex Gateway. +The external agent uses this ID to identify itself to the Ingress Omni 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 Omni Gateway -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. +Agents that aren't protected by a managed Omni 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. + 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. +. To visualize runtime edges and performance metrics, protect the agent with a managed Omni Gateway on the relevant path (ingress or egress), then generate traffic. [[search-agent-network]] == Search the Agent Network