Remote workflows

Remote Logging and Archives

Stream logs from supported development builds and export sessions in the right format for the handoff.

Editor setup
Development-build setup
Recommended workflow
Export formats
Saved log database settings

Remote Logging

Remote Logging streams Azkar Console logs from supported development builds back into the editor. Release builds do not stream logs.

Editor Setup

Open Window > Azkar Console.
Open Settings.
Select Remote Logging.
Enable Listen for Development Builds.
Use Open Unity Player Connection... to select a discovered player, or Connect by IP... for a manual connection.

The toolbar and status area show remote state as the editor listens and devices connect.

Build Setup

Use a Development Build and enable Azkar Console remote streaming for the player with LogConfig.RemoteLoggingEnabled = true before the player sink initializes. No extra logging API is required beyond using Azkar Console logging in the project.

Recommended Remote Workflow

Start the editor listener before launching the build.
Launch the development build on the target device.
Connect through PlayerConnection or direct IP.
Reproduce the issue.
Bookmark important rows.
Export a filtered view or .azrecdb database for follow-up.

Export and Archives

Open the logs menu from the toolbar to clear, import, and export logs.

Format	Use When
`.azrecdb`	Someone should import and inspect the session in Azkar Console.
CSV	Someone wants spreadsheet-friendly rows.
JSON	External tooling or structured analysis needs the data.
HTML	You want a readable standalone snapshot.

Export Scope

Use Filtered export for the rows currently visible after filters. Use All export for the full underlying log store, ignoring current filters.

Imported .azrecdb databases can be searched, filtered, expanded, and inspected like live logs.

Saved Log Database Settings

Saved log behavior is configured at Window > Azkar Console > Settings > Workflow > Saved Logs.

Control	What It Does
`Saved Formats`	Chooses which session files Azkar writes: `Text (.log)`, `Azkar Database (.azrecdb)`, or `Both`.
`Play Mode Session Files`	Controls how many saved play mode captures Azkar keeps per saved format in the `PlayMode` subfolder. Default is `10`; `0` keeps every play mode capture.
`Editor Session Files`	Controls how many whole-editor-session captures Azkar keeps per saved format in the `Editor` subfolder. Default is `5`; this is on by default so users have a longer support and post-crash review trail.
`Database Durability`	Controls `.azrecdb` recovery behavior only. It does not change which files are written.

Durability Mode	Behavior
`Fast`	Lowest overhead. `.azrecdb` writes stay asynchronous, and recent rows are most at risk in a hard crash.
`Balanced`	Default. Asynchronous `.azrecdb` writes plus periodic page sealing after the configured count or interval.
`Crash Forensics`	Most recoverable. Blocks while writing and disk-flushes each log frame/page, so it can slow heavy logging.