Struct LogsResponse 

pub struct LogsResponse {
    pub events: Vec<Value>,
    pub next_cursor: Option<(String, String)>,
    pub next_cursor_line_offset: Option<u64>,
    pub next_segment_cursor: Option<String>,
    pub at_end: bool,
    pub incomplete: bool,
    pub persistence_enabled: bool,
    pub daemon_started_at: String,
    pub attribution_keys: Vec<String>,
}

Fields

events: Vec<Value>

next_cursor: Option<(String, String)>

👎Deprecated since 0.8.0:

tie-breaks by lexicographic id and can silently drop events; use next_cursor_line_offset / until_line_offset instead. Removal tracked in zeroclaw-labs/zeroclaw#8012.

next_cursor_line_offset: Option<u64>

Byte offset past the last event on this page. Pass back as ?until_line_offset= on the next request to resume without re-scanning already-read bytes.

next_segment_cursor: Option<String>

Composite segment-aware cursor for the oldest event on this page. Pass back as ?until_segment_cursor= on the next request to paginate across segment boundaries (active file + rotated archives). Supersedes next_cursor_line_offset for rotating-mode deployments with multiple retained segments.

at_end: bool

True when the file was fully scanned for this filter.

incomplete: bool

True when a retained segment could not be read and was left out of this page. at_end then means “no older events among the segments that could be read”, which is weaker than “no older events exist”, so a client that stops paging on at_end should present the history as partial.

persistence_enabled: bool

Whether this daemon is persisting the runtime trace. An empty event list is otherwise ambiguous between “no matches” and “logging disabled”.

daemon_started_at: String

Daemon start time so callers can implement “since daemon start” without an extra /api/status round-trip.

attribution_keys: Vec<String>

Canonical attribution-field names — ATTRIBUTION_FIELDS plus, for each entry in COMPOSITE_PREFIXES, the bare prefix and its <prefix>_type / <prefix>_alias decomposed keys. The dashboard reads this instead of enumerating schema fields client-side.

Trait Implementations

impl Debug for LogsResponse

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Serialize for LogsResponse

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.