Anypoint Visualizer enables you to view, understand, and make decisions about your application network. Anypoint Visualizer displays views of different aspects of an application network graph. You can use this graph to explore your application network, identify problems, and make decisions. Use cases for Anypoint Visualizer include architectural review and compliance, troubleshooting, and security.
Anypoint Visualizer provides a graphical representation of the APIs, and Mule applications, and third-party systems within your application network. The data displayed in the graph is dynamically updated and does not require prior configuration. Additionally, the data displayed is secure where only users with the proper permissions can view the application network graph.
The following image shows how a typical application network appears in Anypoint Visualizer.
In this image, each node of the application network is represented by a box. Connections between the nodes are represented by arrows.
Anypoint Visualizer provides a real-time view of your application network. It only displays nodes for applications or APIs that are running and discoverable. It also displays third-party service that are invoked by a Mule API, proxy or application. The connections between nodes are based on traffic between applications or APIs that occurred in the last seven days. If an application appears in multiple workers, they appear as two distinct nodes in the graph.
Anypoint Visualizer also enables you to view CPU and memory usage for each node within your application network.
To access Anypoint Visualizer, you must have have the right permissions. See Setup Anypoint Visualizer for information on how to configure permissions.
Anypoint Visualizer collects data from the Mule applications, APIs and proxies deployed to discover all incoming and outgoing connections through an embedded plugin. As long as the application, API, or proxy is running on a supported Mule runtime, it is discovered along with any associated dependencies. See How Anypoint Visualizer Collects Application Data or additional information on how Anypoint Visualizer collects data displayed in the graph.
From Anypoint Visualizer you can select which environments you want to view, arrange applications in layers, inspect their operational monitoring information, and customize the labels displayed for nodes and connnections. See Using Anypoint Visualizer for more information.
Note: Anypoint Visualizer currently only supports Mule Applications, APIs and proxies deployed in CloudHub. For more detail about support for on-premises applications plase contact your customer success representative.
The following use cases provide examples of how you can use Anypoint Visualizer.
Discussing Current Design State: Enterprise architect Kara has developed a plan for how the architecture she’s responsible for will accommodate a new product. She needs to capture its current state so she can plan the transition and get buy-in from stakeholders on her proposal.
Implementing API-led Connectivity: Site reliability engineer Tom is tired of maintaining several separate connections to Salesforce. He wants to identify redundant point-to-point connections so he can come up with requirements for a new process API.
Exploring the Application Network: Anypoint Visualizer provides a real-time view of the application network. This means that architects and product owners can see how the application network evolves explore the appliation network to discover and plan how to unlock data and break down siloed systems, knowing that the visualization is always up-to-date.
Define API-Led Connectivity Classifications: Anypoint Visualizer enables you to assign the nodes of the graph into layers. This enables you to quickly inspect if the APIs are correctly categorized, and if the architectural principles of API-led connectivity are being followed.
Accelerating time-to-production: Architect Kara can see how projects are being built from the development environment, throughout test, staging, and production. This allows Kara to review the architecture as the code is being deployed and rise any concerns to ensure that best practices and agreed upon architecture are being followed without waiting for the documentation to be generted.