
Search the Journal.
Time windows, text queries, object history, and analytic views over Trie-Trunk.
Try It Out
Query Syntax
Builder and pipeline syntax share one query model.
Definitions guide field and value completion.
events.query()
.where(level, ==, error)
.search("timeout")
.order(timestamp, desc)
.page(50)events query
| where level == error
| search "timeout"
| order timestamp desc
| page 50Query Paths
Time, object identity, and text each have
a useful way into the journal.
Time & Text
Bound a search by time, then refine by fields or text. Collect the matching hours for local investigation.
Time Trie + TantivyObject Replay
Follow one object’s revisions. The optional collection index supports history and replay without rebuilding the full object.
collection.idx → WritesAnalytics
Render counts, errors, and duration distributions from summaries. Daily totals also feed weekly, monthly, and yearly rollups.
.sum → Analytic ColumnsRetention is configured per resource and branch. Completeness and lost events remain visible. Scheduled reports and external alert delivery are still planned.
The Research Workspace
The SharedWorker coordinates local datasets. Complete hours and cached daily summaries can be reused as you refine an investigation.
Object History is available when collection indexing is enabled. Lost Events surface rejected records. Session state preserves the research workspace across refreshes.
Try the Current App