Filtering and Bookmarks

How Filters Compose

A row must pass the active search, severity controls, and structured filters to remain visible. Highlight rules mark matching rows after visibility is decided. Start broad, then add category, tag, alias, source file, thread, or highlight rules as the investigation narrows.

Filters narrow the visible view without changing capture order, while highlights make matching rows stand out without hiding nearby context. The live log list stays chronological, so causal context, autoscroll, selection, and collapsed repeats remain predictable while you investigate.

Search

The toolbar search field can match message, header, exception message, and stack trace text. Use Source filters for caller file and line filtering. Use regex mode when the search needs pattern matching.

Default shortcut: Action+F focuses search. Action means Command on macOS and Control on Windows/Linux.

Filters Menu

• Open Filter Builder
• Clear Volatile
• Clear Everything
• Errors Only and Warnings + Errors
• Saved presets and Save Current As...

Default shortcut: Action+K opens the Filter Builder.

Filter Builder

Use the Filter Builder for structured filtering and highlighting by category, tag, alias, thread, source file, file/line context, and dragged Unity contexts. Category, tag, and alias rules come from the metadata attached through AzCon.

Alias filters are grouped as static aliases and dynamic aliases in the UI, which helps separate project-defined systems from identities discovered during play. The full Filter Builder page covers the builder layout, summary chips, highlight colors, striped multi-rule rows, presets, context rules, source peeking, and practical workflows.

Clear Volatile vs Clear Everything

Presets

Save a filter setup as a preset when you repeatedly inspect the same slice of logs, such as networking warnings, gameplay errors, highlighted quest rows, or one subsystem. Applying a preset replaces the current filter and highlight state.

Promote rules to persistent filters or persistent highlights when your team should keep using them across volatile clears. Keep experimental narrowing and color marking as volatile rules while you are actively debugging.

Programmatic Filters

Custom tooling can build LogFilter values directly. Category and alias filters use names; tag filters use TagMask. Include sets show matching rows, while exclude sets hide matching rows even when another rule would include them.

using Azkar.Console.Filtering;
using System.Collections.Generic;

var filter = new LogFilter
{
    Categories = new HashSet<string> { AzCon.Category.Network.Name },
    ExcludedCategories = new HashSet<string> { AzCon.Category.Performance.Name },
    FilterAliases = new HashSet<string> { "Server", "Client A" },
    ExcludedAliases = new HashSet<string> { "NoisySpawner" },
    FilterTags = AzCon.Tags(AzCon.Tag.Create("Combat"), AzCon.Tag.Create("Boss")),
    ExcludedTags = AzCon.Tags(AzCon.Tag.Create("Verbose"))
};

Tag include filters match rows with any tag in the mask. For custom filter logic, use TagMask.Contains, MatchesAny, or MatchesAll depending on whether one tag or every selected tag must be present.

Create and Navigate Bookmarks

Bookmarks save important log entries so they stay easy to revisit even while the live view changes. Create a bookmark from the row star, row menu, or default shortcut B.

Bookmark Shelf and Handoffs

The Bookmark Shelf appears above the live log view when bookmarks are available. Bookmark entries can include notes and source actions. When a bookmark captured a useful filter state, use Restore Filters to return to that view.

Export bookmark JSON when you only want to share saved notes and rows. Use .azrecdb when the receiver should inspect an importable log session.