The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The application monitoring module performs the task of overload detection and load monitoring. It maintains the latest statistical counters for reports being run, scheduled, response times, and so on and sends email and logs appropriate errors if any statistics exceeds (or falls short of) its configured value.
Cisco Insightv2 components support common standards for server hardware, software monitoring, operation, and maintenance. The same information is viewable via WEB UI as well.
This chapter contains the following sections:
You see various metrics about the current performance of the application and system on which the application is running.
Information that can be monitored is categorized in to the following categories and metrics:
•User statistics such as:
–Number of logged-in users
–Number of reports per user session (min, max, and avg)
–Favorite-reports per user (min, max, and avg)
–Scheduled-reports per user (min, max, and avg)
•Report performance statistics such as:
–Report transactions (from each kind - user-generated and automatic)
–Report response time (min, max, and avg)
–Failed report transactions.
•General performance and capacity such as:
–CPU Utilization
–Memory Utilization
To access and display the Performance tab, click the Monitoring icon on the module launcher. You see a screen shot similar to the following:
Figure 7-1 Performance Statistics
To access and display the Logging tab, click the Monitoring icon on the module launcher.
Using this tab, you can monitor the problems occurring in the system.
Figure 7-2 Logging Tab
You can also search logs based on following parameters:
•Start and End date and time
•Log message
•Log priority