Kadiska Application Performance Scoring Dashboard Overview (AppDex)
Kadiska has introduced a new application performance scoring dashboard for all monitored applications. The scores are based on AppDex, which is an open standard used to calculate the application performance index for both single and multi-page web applications (SPA, MPA), which are identified automatically by Kadiska.
AppDex takes into account three types of user experience levels: good, tolerable, and critical. Kadiska calculates AppDex scores based on API call processing time and loading metrics, and takes historical data into account to determine whether an application's performance is improving or degrading.
The scope of degradation is determined by the number of users by category. Click on the related zone in the application score widget to access the application dashboard, AppDex score, API call processing analysis page, and resources analysis dashboard to analyze resource errors.
Learn more at docs.Kadiska.com
SUMMARIZED VIDEO TRANSCRIPT
The new product release presents a main application performance scoring dashboard on the Kadiska platform's homepage. The dashboard lists all monitored apps, default sorted by name, but can be arranged by performance to highlight the worst-performing apps first. A search bar facilitates the search for specific apps, like Microsoft Teams.
Widgets by default show only the score, but hovering or clicking on "show details" reveals application performance details. The core of this system is AppDex, an open-standard metric that calculates an application performance index based on a performance target and user connections. AppDex differentiates between good, tolerable, and critical user experiences. The platform automates the recognition of single-page and multi-page applications, considering API calls for the former and browser refresh time for the latter, for example, Google Mail.
The performance metric's target value is derived from historical data in our database. For instance, the AppDex calculation targets 85 milliseconds as the threshold. The AppDex score, contingent on the timeframe, is based on the API call processing time for single-page apps and the loading metric for multi-page apps. Kadiska uses historical data to evaluate application performance, identifying trends over selected timeframes.
The degradation's scope is determined by categorizing AppDex users. As an illustration, if an app like Miro has a severely degraded AppDex score, the user breakdown might show that two users face critical issues, four have a good experience, and one encounters problems. Clicking on the user breakdown leads to the application dashboard, which filters by application and presents connectivity and performance data.
Troubleshooting for slow apps is simplified by clicking on the AppDex score, leading to the API call processing analysis page or webpage analysis dashboard. Lastly, we calculate the failed resource transactions percentage. For instance, Google Meet had a 7.2% failure rate in resource-related transactions. Clicking on the failure rate value directs to the resources analysis dashboard, which focuses on error rates and resource sorting by errors.