My Betty Blocks
My Betty Blocks
In this article
This article contains all the information you need to know about each setting within the Logs interface.
Robert van Boesschoten
Last updated: 17-10-2019
The logs interface lets you keep track of all the logged action events, errors, warnings, used variables and debugging information. All you have to do is enable the debug logging and/or Log execution of the Action event or Page you want to monitor. More information can be found here: What are Logs and HowTo read them and the Action Reference.
In the logs interface, you’ll find the following buttons and settings which all will be explained in this article
Clear log: By clicking on this button all logs will be cleared. If not cleared manually, a Log will be available for two months. After this period the log is automatically cleared!
Questionmark [?]: By clicking this button, a new panel pops-up. This panel will present an instruction video of “Welcome to the logging panel”
All: Sets the filter to show all of your logs.
Error: Sets the filter to show all of your logs with an Error.
Warn: Sets the filter to show all of your logs with a Warning.
Info: Shows all relevant information about the presented Logs.
Debug: Sets the filter to show all of your logs of all actions, events, and page where Debug action and events/Enable debug logging is enabled.
Show logs between: Filter your logs by date.
You can set the filter by: `Today`, `Yesterday`, `Last 7 days`, `Last 30 days`, `This Month`, `Last Month` and if all of that isn’t enough, you can choose to filter between two specific dates, using a `Custom` filter.
Eraser (red button): Removes the date filter of the Show logs between.
Refresh: Pressing this button (or `R` on your keyboard) reloads the grid, retrieving the latest logs if they haven't loaded yet.
The next part of the interface we can define in several sections.
This section shows the exact date and time when your Log was created.When the log is unfolded, this section shows the time (in seconds) it took to get to that point from the initial start.
This section contains all information about the logged process. Each log message is different, and can be built up from a certain set of components. Those components are:
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. Does affect real data, though, so use with caution.
Start executing: The log originates from an Action.
Incoming: The log originates from a Page.
Links: Clicking a link (blue text), will open a separate browser tab which takes you directly to the Action (event) or Page.
Fold/Unfold: When unfolding the first message line you’ll see that every log item line starts with the action event type which is executed at that 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.In the Params field, you can find 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 we received, often the reason why we performed a request in the first place.
The Variables section shows you all variables which are used in the action event or page.
Note: A variable will only be shown in the logs if it's actively used in the action or page. To enforce a variable being parsed/loaded, turn off LazyLoading on the variable with advanced settings enabled.
You can look at the value of your variables by clicking them. You can also expand all variables available at a specific log line by clicking the ellipsis-button (the three dots) in the variables column.
The variables are presented in different colors:
Variables defined at the beginning of your Action or Page, available throughout the entire process.
Global variables, available throughout the entire application. Also includes variables used to point out the active user from an Authentication profile.
Variables which contain a result from an event, defined as the As variable (in Create and Http request events).
Variables defined within an Action event, only available within its scope. For example, a variable defined in the `true` flow of a condition isn't available outside of the `true` flow, as it also wouldn't be available if the action went through the `false` flow.
When an action event is executed in a foreground process (background by default), the current user is displayed. Read more about Background processing in the Action Reference documentation.
In this article