Azkar IndustriesUnity Asset Store Package
Unity diagnostics
Azkar Console provides an editor console and the AzCon structured logging API for Unity. It captures Unity-originated logs through supported public threaded-event and compiler-diagnostic paths, and includes metadata filters, row highlights, bookmarks, session archives, remote logging for development builds, and an optional dockable inspection Workbench. It does not inspect or control Unity's private native Console rows.
Important before purchase
Azkar Console uses documented public Unity APIs. It does not enumerate Unity's existing native Console history, recover private native-row context, select an exact native Console row, clear Unity's Console, or invoke hidden manual-IP PlayerConnection methods. These are Asset Store compliance boundaries, not paid-tier restrictions.
Read the complete limitation list and Unity guideline referencesSecurity and privacy
Messages, exceptions, stacks, source paths, metadata, bookmark notes, device details, archives, exports, and clipboard text can expose project or personal data. Do not log passwords, keys, tokens, credentials, private keys, health or financial data, or other secrets. Redact data before copy, export, commit, or support sharing. Customers remain responsible for consent, access, retention, and deletion.
Clearing visible rows unmounts imported databases from the current console, but it does not delete their source `.azrecdb` files, preferences, bookmarks, imported fonts, automatic logs, manual exports, or clipboard contents.
Remote trust boundary
Remote logging uses Unity PlayerConnection. Azkar Console validates its frames and peer state but adds no independent application-layer authentication, confidentiality, or integrity guarantee. Treat remote labels and payloads as untrusted input. A pre-freeze scan of the current Azkar-owned source and locally built Azkar assemblies found no product telemetry or automatic Azkar Industries upload implementation. The final candidate must repeat that scan; this is not candidate-bound evidence. Unity services, customer-owned ILogSink integrations, and other project packages are outside that claim.
Finite saved-log storage
Text segments default to 32 MiB, database segments to 64 MiB, and both share a 128 MiB session budget. Editor and Play Mode folders default to 512 MiB and 256 MiB, inactive recognized files expire after 30 days, and writes preserve the greater of 256 MiB or 5% of the volume as free space. Low-space, quota, or disk-write faults pause the affected bounded sink, count drops, coalesce warnings, and retry slowly into a fresh segment.
Unity diagnostics
Azkar Console adds a separate editor window for reviewing live logs, structured metadata, source details, bookmarks, session archives, and development-build connections. Unity-log capture is configurable. For Unity-generated entries, Unity's Console remains available and is authoritative for context-object pinging.
Compatibility
Azkar Console works on Unity 6 (6000.0 or newer). The distributed build's Technical Details identify the exact Unity patch and Burst/Collections combinations qualified for that release. Explicit Unity object contexts attached through AzCon use a version-neutral typedLogContextId.
Requires Unity Burst and Collections packages. Because Azkar Console is delivered as a regular .unitypackage, install them through Unity Package Manager if they are not already present.
Console operations
Attach categories, tags, aliases, headers, source information, and Unity object context to log entries.
Show or hide Level, Frame, Time, Alias, and Category while Message stays visible; responsive layouts preserve your configured choices.
Configure the live viewHighlight matching rows without removing surrounding entries; multiple matching rules share the row background.
Keep multi-log details, checkbox-aware bulk copy, source preview, Trace occurrences, and the Filter Builder in one optional dockable workspace without giving up separate utility windows.
Read the Workbench guideExport and import Azkar Console .azrecdb database files, or export the current view as CSV, JSON, or HTML. JSON logs are export-only.
Uses documented public Unity APIs. Native Console history import, private context recovery, exact native-row selection, Unity Console clearing, and hidden manual-IP attachment are intentionally not included.
Read the compliance disclosure