Application details
From the dashboard, click an application to drill down for further detailed information.
Select the time from the list to view:
-
Transaction Logs – Enables you to view the detailed transaction for the application, such as response time > 500 ms, 5xx errors, and so on.
-
Performance – Enables you to view the application performance such as app score and the issues that are affecting the app score.
-
Key Metrics – Enables you to identify the application usage.
-
Web Insight – Enables you to visualize the complete application from the perspectives of performance and usage.
-
Security – Enables you to view the application WAF violations.
After you select the time from the list, the following application details are displayed:
-
App Score – The application score for the selected time duration and the current issues that are impacting the application score. The final score is calculated as 100 minus total penalty.
-
All Services – The services that are bound to the application. You can view the service status that is in Up, Out of Service, or Down.
Click to view the service details.
Select the service and click:
-
Bound Servers to view the details of the servers associated with the service.
-
Bound Monitors to view the details of the monitors associated with the service.
-
-
Issues - The current issues that are affecting the app score. You can view the following issues:
-
Response Time
-
Server error (5xx)
-
Active services
-
Response Time
This issue detects when the application response time to respond to client requests deviates from the configured threshold value. Click the Response Time tab to view the issue details.
Under Details, you can view:
-
The graph indicating the total events for the selected time. Click to apply filter and view details
-
The date and time that the issue has occurred.
-
The total occurrences for the selected time.
-
The issue severity such as low, medium, and high.
-
The detection message indicating the total transaction response time exceeding the configured threshold value.
Active Services
This issue detects when the % of active services bound to the virtual server is lesser than the configured threshold value. Click the Active Services tab to view the issue details.
Under Details, you can view:
-
The graph indicating the total events for the selected time duration. Click to apply filter and view details.
-
The date and time that the issue has occurred.
-
The total occurrences for the selected time duration.
-
The issue severity such as low, medium, and high.
-
The detection message indicating the % of active service sessions and the configured threshold value.
Server error 5xx
In some scenarios, the web server responds with status codes when it is unable to handle the requests for reasons such as invalid requests, temporary overloading, or server maintenance. These errors are displayed with error codes, which define various scenarios of the errors. For example:
-
502 Bad Gateway: The server is acting as a gateway or proxy and received an invalid response from the upstream server.
-
503 Service Unavailable: The server is unavailable. The servers might be overloaded or down for maintenance.
-
504 Gateway Time-out: The server is acting as a gateway or proxy and did not receive a timely response from the upstream server.
These can be temporary conditions, but sometimes you must implement a corrective measure on the webservers to make the webpages up and available.
Using the Server Error 5xx indicator, you can view these failures and take decisions about corrective actions to overcome the issues and ensure the client requests are served and the webpages are always available.
Select the Server Error 5xx tab to view the issue details.
The Recommended Actions to troubleshoot the issue are:
-
Configure L7 monitors with appropriate parameters for the server that responds with 5xx errors. A monitor is an entity that tracks the service health. The appliance periodically probes the servers using the monitor bound to each service. If a server does not respond within a specified response timeout, and the specified probes fail, the service is marked DOWN. The appliance then performs load balancing among the remaining services.
-
Troubleshoot the server.
Under Details, you can view:
-
The time that occurred the unstable server anomaly.
-
The service/service group name
-
Total occurrences
-
The anomaly severity such as high, low, and medium.
-
The detection message indicating % of the responses from this service reporting 5xx errors.