Copying and exporting log entries

The log can be copied to the clipboard for pasting into a message, exported as a file for an attachment, or cleared to start fresh.

Copying to the clipboard

Right-click the log grid for the context menu:

• Copy row - the selected rows, each formatted as [timestamp] [level] [category] message.
• Copy cell - just the focused cell.
• Copy all rows - every visible row, columns separated by commas.

The clipboard format is plain text suitable for pasting into a chat client, a ticket, or a spreadsheet.

Exporting to a file

Pick Export to file... from the context menu. A save dialog opens with the default extension .csv.

Supported formats (chosen by the Save as type dropdown):

• CSV (.csv) - opens in Excel; useful for sorting and pivoting.
• JSON (.json) - one object per entry; useful for piping into a log-analysis tool.
• Text (.txt) - one entry per line, columns separated by whitespace.

The export contains exactly the visible rows in the same order as the screen. Hidden rows (filtered out, or scrolled out of the in-memory buffer) aren't included.

Clearing the log

Clear log in the context menu (and as a separate action on the application's main action list) removes every entry from the in-memory log. The on-disk log file is not touched; clearing the view only resets the tab.

Use Clear when you want a clean baseline before reproducing an issue.

Attaching the log to a support ticket

The recommended workflow:

1. Set the level buttons to All.
2. Click Clear log.
3. Reproduce the issue.
4. Export to JSON or CSV.
5. Attach the file to your ticket.

A focused log starting just before the failure is more useful than a giant log from yesterday.