Web Apps Metrics

This section gives an overview of the status of all web applications enabled within the organization. Its aim is to provide quick access to key application information, like the total requests, average latency, and number of errors, allowing early detection of potential issues.

Enabled Applications Table

This view presents a list with data corresponding to the last 24 hours:

• Name. Main identification of the application.
• Total Requests. Number of requests made by users.
• Average Latency. Mean response time of the requests.
• Total Errors. Total number of errors recorded in the requests.
• Description. Brief summary of the application
• URL. Web addresses linked to the application.

Web Application Detail

Selecting an application accesses its detail view, comprised of the following sections:

• Details
• Summary
• Reliability
• HTTP Messages
• Metrics by Workspace
• Anomalies
• Organizations

Details

It presents the general information of the web application and its visibility configuration.

Summary Panel

• Created by. User who registered the application.
• Created on. Date and time of creation.
• Updated by. User who modified the information.
• Updated on. Date and time of the last update.

Overview

Includes the following data:

• Name. Main identification of the application.
• Description. Brief summary of the application
• URLs. Web addresses linked to the application.
• Logo. Graphic symbol that identifies the application.

Visibility

Indicates in which organizations or sub-organizations the web application is available.

Summary

Displays access statistics based on the number of requests made.

Time Interval

Data can be filtered by:

• Last 24 hours
• Last 7 days
• Last 14 days

Summary Panel

Shows the following quantitative data:

• Requests
• Errors
• Latency

Charts

Success and Error Rates:

• Two pie charts with success and error rates.
  • The errors are classified as client (4xx), server (5xx), and network.

Requests Evolution:

• A line chart showing the evolution of requests during the selected period.
  • Hovering over a point displays the values corresponding to that date.

Reliability

Presents two line charts that show:

• Average latency (ms) of the total requests to the web application.
• Recorded errors in access.

Information adapts to the time interval, applied filters, and device segmentation.

Time Interval

Data can be checked in the following periods:

• Last 24 hours
• Last 7 days
• Last 14 days
• Last 30 days
• Last 90 days

Filters

Metric Filters enable granular analysis of latency and errors through:

• Property. Report Group, Network, Location, Area, Department, Office, Organization and Error Code.
• Operator. = (Equal to) and != (Not equal to).
• Values. Depend on the selected property.

Segmentation

Allows segmenting graph data based on:

• Property. Report Group, Network, Location, Area, Department, Office, Organization and Error Code.
• Limit. Allows displaying between 1 and 100 divisions of each property.
• Sort. Allows changing the order, in Ascending or Descending manner.

This level of detail helps identify where latency or error excesses occur in device groups.

HTTP Messages

Shows information about the HTTP messages exchanged between the end-user's device and the server when making a request.

Table Content:

• Correct. Indicator of successful (✅) or failed (❌) access.
• Latency. Response time in milliseconds.
• Route. Requested address.
• Workspace. Device accessing the application.
• Report Group. Group to which the device belongs.
• Method. Type of HTTP request.
• Request Timestamp. Date and time of the request.
• Response Error Code. Type of error recorded (when applicable).
• Response Error Message. Detailed error description (when applicable).
• Status. Server response status code.

Time Interval

Data can be filtered by:

• Last 1 hour
• Last 4 hours
• Last 8 hours

Filters

Metric Filters allow analyzing the messages according to:

• Property. Report Group, Network, Location, Area, Department, Office, Organization and Error Code.
• Operator. = (Equal to) and != (Not equal to).
• Values. Depend on the selected property.

Summary Panel

Shows the following quantitative data:

• Requests
• Errors
• Failed requests
• Latency
• Unique devices

Metrics by Workspace

Allows knowing a device's behavior concerning the web application. Table Content:

• Workspace. Name of the device that has made requests to the application.
• Report Group. Group to which the device belongs.
• Total Requests. Number of requests made to the application.
• Average Latency. Number of milliseconds elapsed between the request and response.
• Total Errors. Number of errors recorded in the requests.

Clicking on the device or report group name accesses the detail of its information.

Time Interval

Table data will change depending on the selected time period:

• Last 4 hours
• Last 8 hours
• Last 24 hours
• Last 48 hours

Anomalies

This section allows analyzing the web application's behavior and comparing its usual operation with that observed in the last 48 hours.

The contrast between both behaviors facilitates detection of anomalies in the following indicators:

• Total requests
• Total errors
• Average latency

info

To determine the values considered as "usual", the model performs pre-training based on historical data between 15 and 30 days. From this analysis, the normal range of each metric's behavior is established.

Summary Panel

Shows the following quantitative data:

• Total anomalies
• Request anomalies
• Error anomalies
• Latency anomalies

Anomalies in total requests

This chart shows the number of requests made to the web application compared to the expected normal range over a 48-hour period.

• Blue shadow. Represents the typical number of requests under normal conditions.

• Blue line. Indicates the number of requests detected over the last 48 hours.

• Red shadow. Points out the time intervals where an anomaly has been detected.

  When the blue line exceeds the blue-shaded area, it means more requests than usual have been recorded, which may indicate anomalous behavior.

Anomalies in total errors

This chart shows the number of errors recorded while processing requests, compared with the expected normal range for a 48-hour period.

• Blue shadow. Represents the usual number of errors occurring under normal conditions.

• Blue line. Indicates the number of errors detected over the last 48 hours.

• Red shadow. Identifies the time intervals where an anomaly has been recognized.

  When the blue line exceeds the blue-shaded area, it is interpreted as more errors than expected have been recorded, possibly indicating an anomaly.

Anomalies in average latency

This chart shows the evolution of the average latency of the web application compared with its normal range during a 48-hour period.

• Blue shadow. Represents the usual average latencies.

• Blue line. Shows the average latencies recorded over the last 48 hours.

• Red shadow. Points out the time intervals where an anomaly has been detected.

  When the blue line is above the blue-shaded area, it is interpreted as the application having shown response times higher than usual, indicating a performance anomaly.

Legends

Graph legends allow toggling data display:

• Normal range. Shows the normal range.
• Request count* Shows the real detected data.

Hovering over a point in the graph displays the exact values corresponding to that date and time.

Tables

Below each graph, data is presented in table format with the following fields:

• Date. Date and time when the anomaly is recorded.
• Value. Recorded value.
• Lower bound. Normal lower limit.
• Upper bound. Normal upper limit.

Organizations

Allows tenants to enable or disable the web application in their sub-organizations.

The table displays the following fields:

• Name. Organization and sub-organization.
• Enabled. Current status (yes / no).
• Enabled on. Date and time of enabling.
• Enabled by. User who performed the action.

Enable or disable a web application in a sub-organization

From this tab, you can choose the sub-organizations that will have access to the web application.

1. Select one or more sub-organizations in the table.
2. Click Enable or Disable as applicable.

Actions on Web Applications

This option menu allows:

Enable or disable a web application

From this option, you can enable or disable a web application in the organization. You can find more information here.

Edit

Opens a form to manage the application's information:

Overview

• Name. Main identification of the application.
• Description. Brief summary of the application
• URLs. Web addresses linked to the application.
• Logo. Graphic symbol identifying the web application.

Visibility

Defines in which organizations or sub-organizations the application will be available. Making a web application visible does not imply it is enabled.

If visibility is removed in an organization, the application will become unavailable, even if it has historical data.

Delete

When removing a web application:

• It will no longer be visible in all organizations where it was available, except in the organization where it was created.

• In the organization where it was created:

  • It remains visible but stops collecting new data.
  • Historical data will be available for up to 120 days.
  • After this period, it will also cease to be visible.

• If no data has been collected, it disappears immediately from all organizations.