How to Create Dashlets in Entuity Network Analytics (ENA)
This article shows you how to create dashlets by drawing data from other dashlets and extending the dynamic export capabilities to meet your own specific requirements in ENA (Entuity Network Analytics).
- Create Dashlets
- Dynamic Dashboards
- Entuity Network Analytics
- Network Management
In this example, we’re going to leverage the configuration where the dashlets source is taken from other dashlets. The default setting for a dashlet source is the Dashboard Context.
As you see the image below, “ce01” is the current Dashboard Context and each dashlet uses that context as its source. You can also set the dashlets source to a Fixed Object as we’ve shown in other examples.
But for this article, we are going to learn about how to create a dashboard where the dashlets source comes from a selection in another dashlet. There’s already a good example in the system that we can start with. Let’s go to the QoS dashboard for CA just under All Dashboards Menu.
With the exception of the Policy Maps, all of the dashlets are empty.
If the Policy Maps were selected, you can see the associated Class Maps.
If I take it a step further, I can select a Class Map and show all the performance metrics for that Class. This is a good example that’s already in your system and you can use it as a base to create your own dashboard.
ENA Tips: When select one of Policy Maps or Class Maps, remember don’t click on the blue hyperlink and just select the line. If you have any questions about the individual dashlets, just Select the Help Menu and it will take you to the Help Center.
Let’s look at another example – Device Comparison Dashboard. I am going to show you how to configure this type of dashboard at the View level. Here is the interface of the dashboard which allows me to select two devices in the View and compare performance metrics for each one. These Device Dashlets (Device1 and Device2) take their sources from the View in the Dashboard Context and the remaining Dashlets are taking their source from the two devices.
Let’s look at the definition for this dashboard. From the image below, you can see that I’m using a variety of dashlet types.
I’ve added a text dashlet here with some instructions on how to actually use this dashboard that users can use.
I’ve also added two tables that are used to list the devices in each View and these will be the source for the remaining dashlets in the configuration. For the first device table, you can see that the dashlets source is the dashboard. This is important because I want to list all the devices in a View where the View is the context of My Dashboard. I’ve made sure that the device is the object that I want to display and I’ve also added a number of columns to the table to show Device Name, Location and Current Status of the device. I’ve created the same configuration for the second device table in the remaining dashlets.
Next, I’ve set the Dashlet Source to be a Dashlet and then defining which dashlets should be used. For the Port Summary Dashlet, you can see that dashlet is the source and the source dashlet is coming from device 1 (the list of devices). The same thing for the top end flow summary for the second device. The Dashlet Source is a Dashlet and the Source Dashlet is the Device2. This is the same configuration that’s used for the remaining dashlets.
So let’s Exit the Dashboard Editor and take a look to see how this works. I can select ca01 as my first device and select hq01 as my second device. Each device is going to populate its own set of performance metrics and populate each Dashlet that’s associated with that Device. This is a good example of how you can extend the dynamic export capabilities in ENA to meet your own specific requirements.