|
Configuration of MkiNwAppTrafficTest
For each application over the network connected to the target Cisco Meraki, this test reports the amount of data sent and received. In addition, this test reveals the number of clients accessing each application and the number of destinations used by the clients. Using this test, administrators can figure out the destination that is mostly utilized by the application.
The default parameters associated with this test are as follows:
The eG agent collects the required metrics from the target Cisco Meraki by executing API commands using Dashboard API and pulls out critical metrics. In order to collect metrics, the eG agent should be provided with a valid API key. To know how to generate the API key, click here. Specify the generated API key in the API Key text box.
To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
By default, the Report by Destination flag is set to No. This implies that this test reports the statistics of each application, by default. However if administrators want to monitor the individual statistics of each destination corresponding to the application on the network of the target Cisco Meraki, then, this flag can be set to Yes.
This flag appears only when the Report by Destination flag is set to Yes. By default, the Report by Totalflag is set to Yes. If set to Yes, then the test will report measures for an additional Total descriptor summarizing the statistics of all the applications over the network of the target Cisco Meraki.
When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.
|