View – Working with Left Menu
View menu is further categorized into following sub menu/menu items:
- Dashboard: This displays the current Dashboard.
- Application End-to-End View: This section provides end-to-end view of application via Cavisson Executive Dashboard. An Executive Dashboard is a visual representation that gives executives a quick and easy way to view their application’s performance in real-time. Executive dashboard is a powerful tool for executives because they summarize complex information and present it in an easily digestible way.
- Geo Map: This section provides the way to view the Tier status for each store application-wise or for all applications. Each store can have multiple applications, for example: Mobility, Kiosk, POC etc. and each application can have multiple tiers.
- DB Monitoring: This is a powerful feature to measure the performance of each query contributing in a session execution. It provides complete monitoring of MSSQL queries with insights into SQL activity, wait statistics, databases, support services, Temp DB, and high availability. It enables a user to detect such queries, which are consuming more resources as compare to normal ones. Once identified, user can diagnose the issue and perform corrective measures. It also provides monitoring of Postgres query as well.
Clicking the Dashboard option displays the Dashboard with various sections. The detailed description of this window has already been provided.
The detailed description of each section and the operations a user can perform is provided later in subsequent sections.
Application End-to-End View
This section provides end-to-end view of application via Cavisson Application End-to-End View. An Application End-to-End View is a visual representation that gives executives a quick and easy way to view their application’s performance in real-time. Application End-to-End View is a powerful tool for executives because they summarize complex information and present it in an easily digestible way.
Application End-to-End View provides insight into:
- Single view for monitoring application performance
- Real user experience
- Database performance
- Respond to event and alerts
This section provides the way to view the Tier status for each store application-wise or for all applications. Each store can have multiple applications, for example: Mobility, Kiosk, POC etc. and each application can have multiple tiers.
Tier status displays:
- Real Business health based on Alert generated on front tier of application / store and
- Infrastructure health based on alert generated on all tiers of application / store.
Using this functionality, a user can perform the following operations:
- View GeoMap of Stores, Business Health, and Infrastructure health of stores.
- View Tiers as per application of each store so that Tier Status is not cluttered.
- View Stores as per its states (Critical, Major, or Normal) by apply filter.
- Search Store by its name.
- Search Store by application name.
- Create application by grouping Tiers.
- Edit/Delete an application.
- View all applications of each store.
- View Tier Status of every application individualize.
- In Tier status, business health of tier is displayed based on the alerts generated. Alert rule will be configured on KPI (TPS / TPM, Response, Error and order / Revenue)
Viewing Tier Status
To view the tier status, follow the below mentioned steps:
- Go to View > Geo Map, this displays the Store View window.
In the above screen, user is able to see Store location in GeoMap. Store can have Critical/Major/Normal health. Health is indicated by different color, such as Red for Critical, Yellow for Major, and Green for Normal. Health of Store is decided by health of application.
For example, if a store has four applications and if any application’s health is Critical then health of store will be Critical. Therefore, higher severity among the applications of store will decide health of store.
- User has the provision to select data center from the drop-down list.
- If user wants to see business health of store, user needs to select Business option in Health Status By default, GeoMap of store is displayed according to Business Health.
- If user wants to see infrastructure health of store, user needs to select Infrastructure option in Health Status list.
- User can filter stores by selecting desired option (Critical, Major, Normal, Store Name, Store City, or State Name) from Filter drop down list.
- Further, user can filter stores by selecting application name from Select Application drop down list. User can also select more than one application. Only those stores are marked with color, which consists selected Tier.
Search by ID
Using this option, a user can search FlowPaths just like the Application End-to-End View UI. Clicking the search icon opens the Search FlowPath window.
Proceed to search a flowpath as per the procedure mentioned in Flowpath Search section.
This section provides a summarized view of application stats in tabular format. The details include – application name, TPS, Response time, and error percentage.
There is a tabular data, which displays aggregate of KPI parameter (Total transactions, top 10 transactions, total alerts, total good stores, and total bad stores) of all / same application.
User can further execute following actions to view other details:
This section contains various details, such as BT name, overall count, overall percentage, regarding business transactions. User can further perform actions, such as view method-timing report, view DB request report, view flowpath analyzer, and view BT IP summary.
Top 10 Transactions
This section displays top 10 transactions for all or selected application.
This section displays total alerts generated for application(s). Here is an example of ‘Critical’ alerts.
Total Good Stores / Bad Stores
By clicking this link, user can view details of all good stores. The details include – Store name, response time, PVS, and error (%).
Upon clicking the link, the details are displayed in Web dashboard.
Note: User can view the details of Bad Stores in the same manner.
At the tooltip on mouse hover on store name, it displays Store name, name of application (which exists in that store), count of alerts (which are generated in all application with their severity) etc.
Good / Bad Stores
Such stores in which critical alert is generated are termed as Bad stores. Apart from these stores, in which any other or no alert is generated, it is termed as Good stores. Bad Stores are marked by red color and good stores are marked by either yellow or green.
Stats for Good and Bad Stores are also displayed in the form of Pie chart. In this chart, good stores are represented with Green color and bad stores with Red color. User can also view the percentage of each category by doing mouse hover on the pie chart.
Creating an Application
- To create an application, user needs to click the Application Setting icon . This displays the Application Settings screen.
2. Enter application name and select the tier for the application. Then, select front Tier of application. Alert on Front Tier decides the health of application. There is only one Front tier of each application.
3. On clicking the Save button, the record is saved in the tabular format. User can edit or delete the record.
4. On clicking the Store, user is able to view all applications of that store.
In the above screen, user can change icon of application. It displays all applications of the selected store. Application is displayed within a box. Border of the box can be Green, Red, or Yellow as per generated alerts on Front Tier. This color indicates the Health of application. Higher severity of Alert on Front tier of an application is the health of the application.
In the box of application, it displays KPI parameters (TPS, Response, and Error). These KPI parameters is the aggregate of KPI parameters of all tiers of that application.
User can filter application by Health Status by selecting “Business” or “Infrastructure”. Infrastructure health is based on Alert generated on all Tiers of that application and color of application box is changed according to higher severity of alert. Upon clicking the application icon, it displays the Tier Status of selected application.
This section provides details for MS SQL Monitoring and Postgres Monitoring. The description of these topics are provided in subsequent sections.
MS SQL Monitoring
This section provides the capability for profiling MSSQL. Cavisson machine agent establishes a connection with MSSQL database server. After establishing the connection with database, monitor executes some queries to capture the required stats to get the health status of MSSQL. To make connection with MSSQL, user needs to provide connectivity credential to the monitor program, so that it can make connection to the database.
It also provides end-to-end monitoring of MSSQL queries with insights into various aspects, such as SQL Activity, Wait Statistics, Databases, and Support Services.
Implementing effective MSSQL monitoring with NetStorm offers the following benefits:
- Improved application availability
- Increased database performance
- Quick detection of database outages, failures, and table corruption
- Prognostic analysis of storage requirements and index performance
- Provides all information on blocked / blocking queries.
- Provides all types of Wait Stats.
- Provides Query Execution Statistics and Query Plan.
- Provide status for MSSQL services.
- Ability to view data file growth and log growth for databases.
For more details on MSSQL Monitoring, kindly refer the Web Dashboard User Manual.
This section provides the capability for profiling Postgres. Cavisson machine agent establishes a connection with Postgres database server. After establishing the connection with database, monitor executes some queries to capture the required stats to get the health status of Postgres. To make connection with Postgres, the user needs to provide connectivity credential to the monitor program, so that it can make connection to the database. It also provides end-to-end monitoring of Postgres queries with insights into SQL Activity.
For more details on Postgres Monitoring, kindly refer the Web Dashboard User Manual.