Logs

The Logs page is used to view execution records and inspect execution details within a Code Flow.

Studio sessions started within the Code Flow, Agent executions performed while building Docker images, and Code Flow executions created when Docker images are run are listed on this page.

Users can use this page to track execution status, start and finish times, duration, and the user who started the execution.

The View Details action can be used to access the detailed logs of an execution.

Log Types

The Logs page displays records for different types of executions.

The main log types are:

This allows users to track the history of different execution types from a single page.

List View

In List View, log records are displayed in a table.

The following information is displayed:

For an execution that is still running, the Finish Date may display - because the execution has not yet finished.

Sorting

Supported columns in List View can be sorted.

The sorting control in the column header can be used to sort records in ascending or descending order.

The following fields support sorting:

• Type
• Status
• Start Date
• Finish Date

The sorting icon in a column header indicates that the column can be sorted.

Card View

Log records can also be displayed as cards.

Each card contains basic information about the execution.

The three-dot menu in the upper-right section of the card provides access to the available actions for the log record.

View Options

The Logs page supports two different view types:

• List View
• Card View

The view buttons in the upper-right section of the page can be used to switch between the two views.

Changing the view only changes how the log records are displayed.

Filtering

The Filter button in the upper-right section of the page is used to narrow down log records according to specific criteria.

Filtering makes it easier to find execution records with specific properties.

Multiple filter conditions can be used to narrow down the results further.

Active filters can be cleared when necessary to display all log records again.

Execution Status

The status of each execution is displayed on the Logs page.

Different statuses may be displayed depending on the execution type and its current state.

For example:

• Success
• Running
• Cancelled
• Stopped

Success

Success indicates that the related execution completed successfully.

The total execution duration is displayed next to the status.

Running

Running indicates that the related execution is still in progress.

For active executions, the elapsed time can be displayed next to the status.

Because the execution has not yet finished, there is no Finish Date.

Cancelled

Cancelled indicates that the execution was cancelled before it completed.

The duration until the execution was cancelled is displayed next to the status.

Stopped

Stopped indicates that a previously running execution has been stopped.

For Studio Sessions in particular, the related record can be displayed with this status after the session is stopped.

Execution Duration

The duration of each execution is displayed together with its status.

For completed executions, this value represents the total execution time.

For active executions, it represents the elapsed time since the execution started.

For example:

Success | 1s

Running | 1h 57m 13s

Cancelled | 1m 24s

This information makes it possible to track execution times directly from the Logs page.

Log Actions

Each log record contains a three-dot actions menu.

This menu provides access to the available actions for the related log record.

The View Details action is used to inspect the detailed logs generated by the selected execution.

Viewing Log Details

When View Details is selected from the three-dot menu of a log record, the details of the related execution are displayed.

This section is used to inspect the detailed logs generated while the execution was running.

Users can use these logs to examine the operations performed during the execution.

For example, users can inspect:

• Operations performed by the Agent while building a Docker image.
• Execution logs generated by a Studio Session.
• Operations performed during a Code Flow Run.

This is especially useful for tracking how an execution progressed and examining detailed log records when an execution fails or behaves unexpectedly.

Agent Build Logs

When a Build Recipe is executed using the Start action, the Docker image build process is performed by the Agent.

The execution generated during this process is displayed as Agent Build on the Logs page.

Users can use View Details to inspect the detailed logs generated by the Agent while building the Docker image.

The basic relationship can be summarized as:

Build Recipe → Agent → Docker Image Build → Log

Studio Logs

When a Studio Session is started, the related execution is displayed as Studio on the Logs page.

While the Studio continues to run, the record can be displayed with the Running status.

When the Studio is stopped, the execution status and finish time are reflected in the log record.

The basic relationship can be summarized as:

Studio Session → Studio Execution → Log

Code Flow Run Logs

When a Docker image is run using a Run Recipe, the resulting execution is displayed as Code Flow Run on the Logs page.

Users can inspect the execution result, duration, and detailed logs through this record.

The basic relationship can be summarized as:

Run Recipe → Docker Image → Code Flow Run → Log

Pagination

Pagination controls are available at the bottom of the Logs page.

The total number of log records is displayed in the lower-left section.

For example:

Total 214 records

The pagination controls in the center can be used to:

• Go to the first page.
• Go to the previous page.
• Go to the next page.
• Go to the last page.
• View the current page and the total number of pages.

The Rows per page option in the lower-right section can be used to change the number of log records displayed on each page.