How to Leverage the MuleSoft Anypoint Visualizer
Explore some real-life examples of how to leverage the Anypoint Visualizer in your MuleSoft development team.
Join the DZone community and get the full member experience.Join For Free
Mulesoft released their Anypoint Visualizer in 2018, and these are real-life examples of how to leverage the Anypoint Visualizer in your Mulesoft development team.
What Is the Anypoint Visualizer?
MuleSoft Documentation defines the Anypoint Visualizer as:
Anypoint Visualizer displays views of different aspects of an application network graph. You can use the 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, as only users with the proper permissions can view the application network graph.
How to Leverage Anypoint Visualizer
Configure Anypoint Visualizer
- Follow the MuleSoft Setup Directions to enable Visualizer to capture metrics
- Cloud Hub Workers: you will need to enable monitoring (this is not turned on by default).
- Define Anypoint Visualizer layers required to represent your environment. Anypoint Visualizer comes standard with three layers — Experience, Process, and System
- An example is if you use a queue solution for guaranteed delivery, then you may want to create a transport layer between the Experience and Process layers to drag the correct external node there
- Once the layers are completed, you will need to move the components into the correct layer
- Define and Implement Tagging Strategy
- Product or Business Process Tags — For each component in Anypoint Visualizer, you can tag the components that make up a business transaction
- Project- or Story-based — Each component used by a project can be tagged to provide visibility to the components impacted
With the components tagged properly in the Anypoint Visualizer, it can be leveraged to speed up code reviews by highlighting changes made for the story or project. You will be able to quickly validate that the design was implemented at a high level correctly.
With the components tagged by the business process or product, you will be able to use Anypoint Visualizer during performance testing to monitor real-time metrics:
- Average Response Time
- Average Throughput
- Average CPU Consumption
- Average Memory Utilization
With the components tagged by the story or project, you will be able to use Anypoint Visualizer to catch errors during UAT that may not surface and will allow you to validate that negative test cases are actually raising errors.
Anypoint Visualizer Shortcomings
- IBM MQ Connections currently are not displayed
- External queue or storage compoents are lumped together
- So if you are using a queue solution, all the endpoints are lumped together and it doesn't show the details of the connections
- External system connection details are not available
- Inbound queue connections are not currently monitored
- Each component can only be part of one layer
Share your thoughts in the comments.
Opinions expressed by DZone contributors are their own.