Warning!

This is a legacy document. The features described below are only usable within the classic-generation environment.

Currently, Betty Blocks offers faster and more advanced options that are available in next-gen. Before you start working on some new features in your application, consider doing it using the next-gen version. Visit Logs reference and Using the log message step articles to learn more about how next-gen logs work.

Good luck!

Using logs, you can track all of the logged action events, errors, warnings, variable usage and debugging information. You can enable debug logging and/or log execution for specific Action events or pages. This article explains how you can access the log information, how filter logs and what information is collected and displayed.

Accessing logs

You can access the logs for an application:

Opening the Tools (A) menu and selecting Logs (B).
Note: You may be requested to log in again to access the previous environment. You can then access the Logs from the Tools menu.
Clicking on the button Open in previous environment (A) and selecting Logs from the Tools menu.

The details for the current logs are displayed. The default view is of all the logs. You can use the buttons (E) to switch between different views of the logs. You can display all the logs, or Error or Warning logs only.

When you click on the button in the log message details, the details expand to show additional details. For example, you can click on an Error (F) button as shown to display details about the details logged for the selected error. Details such as the page on which the error is occurring and the endpoint that is resulting in the error are displayed as well as the variables (G) involved.

Using the log menu for filtering information

You can use the various buttons available on log menu for filtering the information displayed as follows:

All	Show all the logs for your application.
Error	Show all error logs for your application. Error messages indicate an error in a process and can be combined with an explanation or validation message. When you click on a message, the details for the error message is displayed:
Warn	Show all warning messages logs for your application.
Info	Shows all relevant information messages about the presented Logs. you can click on an individual message to show details.
Debug	Display any debugging related log information. This information is gathered for Actions and/or pages that have debugging switched on.

Filtering logs by date

You can also use the date options (A) to show information for specific days or specific dates (B). Press the Apply (C) button to specify the dates. The logs for the specific dates are then displayed.

You can clear a filter by clicking on the erase button.

Press the Refresh button (bottom of screen) to update the list displayed to show the latest available logs.

Understanding the details presented in logs

The following details the different sections provided in logs and explains the details that are compiled in information displayed.

Time

The exact date and time when your Log was created is detailed. When expanded, the details for the time (in seconds) that it took to get to the specified point from the initial start is detailed.

Messages

Details all information about the logged process. Each log message is different, and can be built up from a certain set of components.

The following details the different components involved:

Duration: Shows how long the action/page took to complete.
ERROR: Indicates an error occurred in the process. Often combined with an explanation or validation message.
WARN: Indicates a warning occurred in the process. Often combined with an explanation.
Debug: Indicates the action/page has Debug action and events turned on, so the whole process is tracked in the logs.
Background: Indicates the action is executed as a Background process, as opposed to Foreground.
Action Trigger: Shows the trigger used to initiate the action.
TEST RUN: Indicates the action is started manually from within the Action interface, as a test. This affects real data and should be used with caution.
Start executing: The log originates from an Action.
Incoming: The log originates from a Page.
Links: Clicking a link opens a separate browser tab that takes you directly to the Action (event) or Page.
Expand/collapse: When you expand a message, each log items starts with the action event type that was being executed at the time.
Request: Opens a modal when Debug action and events/Enable debug logging is turned on. Contains all information included in the request to a webpage or webservice. Includes the used method, the target URL and the target IP address.
The Params field details all values that are sent as payload.

Response: Opens a modal when Debug action and events/Enable debug logging is turned on. Contains all information included in the response from a webpage or webservice. Includes the response code, showing if everything went according to plan, and the content type, telling what kind of response we received. In the Body field, you can find the payload details received which are normally the reason for performing the request.

Variables

The Variables section shows all variables that are used in the related action event or page. A variable is only shown in the logs where it is actively used in the action or page. To force a variable to be parsed/loaded, open the Advanced settings for the variable and set LazyLoading to Off.

Click on a variable to display the value details.

Note: Where available, you can expand the variables available at a specific log line by clicking the ellipsis-button (...) in the variables column.

The following details how the different types of variables are presented in logs.

Grey	Green	Yellow	Blue

Variables defined at the beginning of an Action or on a Page that are available throughout the entire process.	Global variables are available throughout the entire application. This includes variables for identifying the active user from an Authentication profile.	Global variables, available throughout the entire application. Also includes variables used to identify the active user from an Authentication profile.	Variables defined within the scope of an Action event. For example, a variable defined in the `true` flow of a condition.

User

When an action event is executed in a foreground process (background by default), the current user is displayed.