Web application — Performance page
Monitor the application performance to enable proactive detection and resolution of issues, maintain optimal performance, improve user experience, troubleshoot the performance issues, and confirm that the application meets its intended purpose.
| Field | Description |
|---|---|
| Started Sessions | Total number of active user sessions for the application over the last 2 hours, specifically the latest 5 minutes. Note: Active user sessions information is vital for determining the server load. It also helps you to
determine the perfect time for server maintenance. |
| Average session duration | Average amount of time spent according to user in the application over the last 2 hours, specifically the latest 5 minutes. It’s calculated by dividing total time spent across sessions by the total number of users. |
| Page views | Frequency with which the users access or view a specific page within the application. Each visit to a page is recorded as one page view, whether it is by a first-time visitor or a returning user. |
| Field | Description |
|---|---|
| Average response time | Total time taken to respond during the selected time period. |
| Average page load time | Average amount of time it takes to load the page, from initiation to load completion during the selected time period. |
| Average DNS lookup | Average amount of time it takes for a Domain Name System (DNS) lookup to be completed during the selected time period. A lower average DNS lookup time is desirable, as it contributes to faster web page loading and improved overall internet performance. |
| Failed web requests | Set of all requests that either return an Error Code or an HTTP 408 status code or fail to return a Success Code during the selected time period. |
| Successful web requests | Number of times the HTTP requests made by the client (such as a web browser) to a server that result in a positive and expected response. |
| Availability | Measure of the system's operational performance and its ability to be accessible and usable when needed. It’s typically expressed as a percentage, representing the proportion of time the application is functional and available for use. |