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. Development Builds enable player streaming by default. The remote transport does not start in non-development players, even if the saved setting is enabled.

Editor Setup

Open Window > Azkar Industries > 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

Development Builds enable Azkar Console player streaming by default. Set LogConfig.RemoteLoggingEnabled before remote bootstrap only when the project needs to override that default. Set a trimmed, non-empty LogConfig.RemoteClientLabel before bootstrap when a stable player identity is useful; a blank label falls back to SystemInfo.deviceName. No extra logging API is required beyond using Azkar Console logging in the project. Non-development players never start the remote transport; use saved-log persistence or a project-owned transport when release-build diagnostics are required.

Remote streaming and saved-log persistence are independent. Enabling one does not enable the other.

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. Formula-like text cells receive a leading apostrophe; use JSON or HTML when exact source text is required.
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 Industries > Azkar Console > Settings > Workflow > Saved Logs.

Editor sessions and Development Builds default to Both formats. Non-development players default to Disabled and create no saved-log directory, file, or writer thread until the game explicitly calls LogConfig.EnableSavedLogPersistence(...). Repeating the active mode is idempotent; LogConfig.DisableSavedLogPersistence() flushes and closes the built-in persistence sinks.

Control	What It Does
`Saved Log Persistence`	Chooses `Disabled`, `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.