Skip to content

Lynn Reporting - DEBUG

This report describes the purpose of debugging, which is to identify and diagnose issues in the code. It also facilitates monitoring of logged events and errors, as well as the overall health of the application, helping to detect performance issues, critical errors, and potential service availability drops.

Each chart in the report includes an interactive legend that enables a more dynamic exploration of the data. Each item in the legend represents a data group, and clicking on one of these items hides the associated values from the chart, allowing focus on the behavior of the remaining categories and enhancing interpretation.

Debug logs overview

This table provides a summary of the debug logs of the sessions for each of the channels through which interactions have occurred.

  • Tenant ID: Contains the identifier of the tenant.
  • Channel: The channel through which the interaction with the self-service flow occurs.
  • Service: The service number through which the interaction occurs.
  • Criteria: Data that will be used to identify the customer.
  • Criteria Value: Value of the identification data of the customer's service.
  • Date: Start date of the session.

Debug

This diagram represents a debugging flow between different components of the application, specifically in the communication between the Channel Connector and the Lynn Core. The Channel Connector acts as an intermediary that connects external channels (such as social networks, email, SMS, etc.). The communication is not direct; instead, an Azure Service Bus is used. The Channel Connector places messages in a queue, and the Core retrieves them when it is ready to process them. This approach allows the Channel Connector and the Core to be decoupled and facilitates asynchronous communication.

The diagram is organized into columns, which allows for a clear view of how messages or events are exchanged between components in an orderly sequence. Each column represents a different component of the application:

Channel Connector: - ChannelEdge - ChannelAdapter - CommunicationInterface

Lynn Core: - Service Bus - SessionManager - ConversationManager - CognitiveManager - Edge

At the top left, session information is included, such as the date and session ID. This information is useful for identifying the context and environment in which the debugging process took place.

Events or actions are represented by boxes in each column. The vertical timeline allows tracking the order in which events occur within the system.

Arrows connect events between different components, showing how they communicate with each other. These events reflect common operations, such as state validations, session creation and closure, interaction start and end, etc.

Common Phases in the Flow

Start with Status Check: The flow usually begins with a system status check, represented here by a Health or health check event. This ensures that the system is ready to operate before proceeding with the next steps.

Message Exchange Between Components: As the flow progresses, different system modules communicate with each other through events. This may include session management, request handling, interaction creation and termination, etc. This phase can vary in complexity, depending on the purpose of the flow.

Session Creation and Management: In many systems, session creation and management are essential to maintaining interaction context and state. This is reflected here in events that mark the beginning, management, and closure of sessions, ensuring the system maintains information consistency and frees up resources when needed.

Log Source Server

This pie chart illustrates the distribution of connections across different application servers. Each segment of the chart represents a specific server and its proportion relative to the total connections.

Each slice of the pie corresponds to an application server. The size of each segment reflects the number of connections that originated from that server in relation to the total connections.

Log activity

This curve chart illustrates the activity of the logs over time. The curve represents the number of logs based on different time intervals, allowing for the observation of patterns and trends in log activity.

Debugging is the process of identifying, analyzing, and correcting errors (also known as bugs) in software code or system functionality. It is an essential part of the software development cycle, helping ensure that the program works correctly and efficiently.

The X-axis represents time, which is divided into intervals according to the selected time range for display. The Y-axis represents the number of logs, showing how many logs have been generated or recorded in each time interval.

The line or curves in the chart connect the data points and show the evolution of log activity.