Skip to content

Lynn Reporting

Reports are useful for clearly and in an organized manner presenting relevant data about the performance, activities, and usage of the application, allowing users to obtain an overview of the system. Additionally, they help users make informed decisions by presenting accurate and detailed information, identifying trends, patterns, and areas for improvement, as well as detecting problems or inefficiencies within the application and identifying opportunities for enhancement or growth based on data analysis.

Dashboards

The main view of Lynn Reporting displays the main accesses to each of the reports.

Imagen

Knowledge Performance

This dashboard allows you to view the cognitive evaluation results of a tenant over a period of time, which is useful for assessing the efficiency of the tenant's cognitive training. For more details, click here.

Outbound

The dashboard shows the status of the campaigns configured for a tenant. For more details, click here.

Sessions

It displays statistical information related to a tenant's sessions and the corresponding chats, as well as allowing you to view the menus the user interacts with through the self-service flow. For more details, click here.

Health

It offers a comprehensive visual representation to monitor, analyze, and detect potential performance issues both in the tenant and the associated external services. For more details, click here.

Chat

This report is aimed at analyzing chat transfers, as well as the details of the agent who handled them and the transfer engine used. For more details, click here.

Debug

It contains a detailed log of errors, failures, or issues that have been detected during the execution of a self-service flow in a specific tenant. Para acceder a mas información sobre su configuracion y detalle, consulte Aqui

Survey

The dashboard shows the statistical results of the surveys and their outcomes. For more details, click here

Productivity

It allows you to see the operations performed in the flow designer of a tenant. It shows who has created, updated, or deleted each of the elements in your tenant. For more details, click here

Kyubo

It contains the statistical results of the sessions transferred to the platform, as well as data about the activity statuses of the agents. For more details, click here

Data filter

When clicking on any of them, a filter appears that allows users to customize the view of the information according to specific criteria.

  • Tenant: Input field of type Select to choose the tenant from which you want to view the report, using a dropdown list that displays the numbers and names of all available tenants in Lynn.
  • Environment: Input field of type Select to choose the environment from which you want to view the information, using a dropdown list. The environment can be Testing, QA, or Production.
  • Date: Input field of type Select to choose the report's time period. Options include predefined ranges (5 minutes, 30 minutes, 1 hour, today, yesterday, last 7 days, last 30 days, this month), with the upper limit set to the current day. The Customize range option is also available, allowing users to select an exact date and time range using a calendar.
  • Divisions: Input field of type Check to select either all or specific divisions of the tenant that you want to display in the report.
  • Channels: Check input field to select all channels or only those configured in the tenant that you want to display in the report.
  • Services: Check input field to select all or only the specific tenant services you want to display in the report.

Cost of operations

The data used to generate the reports is stored in Azure Cosmos DB, a globally distributed database service that enables the creation of scalable, low-latency applications. It supports various database models, making it highly flexible for different types of applications.

Each report displays the Request Units (RUs), or Units of Request, at the top. In Azure Cosmos DB, each operation (such as queries, writes, reads, etc.) has an associated cost in RUs, which measure the resources consumed by the operations, including CPU, memory, and disk I/O.

The fewer RUs consumed, the more efficient the operation. In Azure Cosmos DB, the cost of operations is directly related to the number of RUs consumed.