Function events 

pub fn events(ctx: &ServiceContext, max: usize) -> Result<Table, Error>

The newest max IPC exchanges: seq, sec, caller, peer, op, outcome.

Rows are in ring order, oldest first. What each column is worth knowing about:

• seq is the EMITTER’S own event number, not a global one, so a dump mixing several services interleaves several sequences and can look unsorted. It is not. A GAP in one service’s numbering is that service’s dropped events.
• sec is seconds since the oldest row shown. The stored value is an epoch second, which says nothing alone; the GAP between rows is what a stall looks like.
• caller is who made the call, as that service DECLARED itself (as_name). A service cannot be asked its own name - identity is not ambient - so an undeclared one reads ?.
• op is the opcode as a NUMBER. Naming it needs knowledge of the protocol being spoken, and only the service speaking it has that. See this function’s source for why guessing is wrong.

max is clamped to what one reply can carry. Ask status how much history exists.

Errors

As metrics.