Skip to main content

Introduction

Last updated 9/02/2025

Record Log Messages​

The Record Log Messages feature allows Five to capture and persist all output generated by

five.log()
calls into a temporary table within the database for the currently active environment, whether development, testing, or production.

Record Log Messages is primarily designed for the testing and production environments. While it can also be enabled in development, this environment relies on the Five Inspector for real-time debugging and log inspection, making Record Log Messages less commonly needed during development.

Purpose​

This functionality is designed to support:

  • Debugging: track application behavior and identify errors during testing and production
  • Monitoring: review logs to understand system performance or workflow execution
  • Issue Investigation: facilitate troubleshooting by providing a historical record of log outputs

Usage​

  • Enable Record Log Messages from the Five interface to start capturing logs
  • Logs are stored temporarily in the database
  • You can download log entries through the Cluster Management and save them locally for further analysis

Since logs are stored in a temporary table, they are intended for short-term use and should be exported if long-term storage is needed.

Executing the five.log() Entries​

Any function containing

five.log()
messages must be attached to an event to actually execute and generate logs. Simply defining the function isn't enough, Five only runs it when the associated event occurs.

Downloading All five.log() Entries​

When enabled, Record Log Messages captures all

five.log()
outputs for the active environment. The download iLog file contains every
five.log()
entry, including iLogKeys, timestamps, and log messages.