Application Log

The Application Log records useful information about BrickSuite activity. It can help confirm that an operation completed normally and provide diagnostic information when something unexpected occurs.

The log is intended to support troubleshooting without requiring you to inspect the BrickSuite database or development tools.

Viewing the Application Log

Open the Application Log from BrickSuite to review recent entries.

Entries are timestamped and assigned a severity such as Info, Warning, or Critical. The message describes the operation or condition that BrickSuite recorded.

Info — normal application activity and useful operational results.
Warning — an unexpected condition that deserves attention but may still allow the operation or application to continue.
Critical — a serious failure that should be investigated.

Normal log activity can include application startup and version information, database initialization, imports and exports, Build operations, Backup / Restore activity, and other significant actions.

The log is diagnostic information, not inventory history. Inventory History records the lifecycle of physical inventory. The Application Log records application operations and diagnostic events.

Opening the Log Folder

Choose Open Log Folder when you need access to the underlying log file outside the BrickSuite viewer.

BrickSuite log folder open in Windows File Explorer

The raw log file can be useful when preserving diagnostic information before clearing the viewer or when a log needs to be reviewed outside BrickSuite.

If you are sharing a log for troubleshooting, review it first and share only the information needed to investigate the problem.

Clearing the Log

Choose Clear Log when you intentionally want to remove the existing application-log entries and begin with a clean diagnostic record.

BrickSuite asks for confirmation before clearing the log. If the existing entries may be useful later, preserve the log file before confirming the operation.

Clearing the Application Log does not clear BrickSuite data. It does not delete Workspaces, Storage, inventory, movement history, Builds, requirements, or allocations.

A Useful Troubleshooting Technique

When a problem can be reproduced consistently, a clean log can make the relevant events much easier to identify:

Preserve the current log if needed
          |
      Clear Log
          |
Reproduce the problem once
          |
Open Application Log
          |
Review the new entries

This produces a smaller diagnostic record focused on the actions immediately surrounding the problem instead of requiring you to search through unrelated earlier activity.

What to Look For

Start with entries at the time the problem occurred. Look for Warning or Critical messages and for Info entries immediately before them. The preceding normal operation often provides useful context for understanding what BrickSuite was doing when the problem occurred.

When reporting a problem, it is helpful to describe the steps that produced it and preserve the corresponding log information.

Application Log and Backup / Restore

The Application Log can help confirm Backup / Restore operations or provide diagnostic information if one fails. The log itself is not a substitute for a database backup.

See Backup / Restore for protecting the BrickSuite database.

Application Log and Inventory History

Use the two histories for different questions:

Application Log
  What was BrickSuite doing?
  Did an operation report a warning or failure?

Inventory History
  What happened to this physical inventory?
  Was it imported, moved, lost, or otherwise changed?

See My Inventory for inventory movement history.