GET /api/log/info/

Get an event-log summary.

Auth: Bearer.

---

Response 200

{
  "capacity": 4096,
  "total": 250,
  "pending": 3,
  "oldestSequence": 0,
  "lastSequence": 250,
  "totalBySeverity": {
    "debug": 12,
    "info": 180,
    "warning": 40,
    "error": 15,
    "fault": 3
  },
  "pendingBySeverity": {
    "debug": 0,
    "info": 1,
    "warning": 1,
    "error": 1,
    "fault": 0
  }
}

Response fields

Field	Type	Required	Description
capacity	number	yes	Maximum ring-buffer capacity
total	number	yes	Number of available events
pending	number	yes	Number of unacknowledged events in the current power session
oldestSequence	number	yes	Sequence number of the oldest available event in the ring buffer. For UI pages showing the oldest events, this is the primary indication that the old edge of the window has actually moved because events were evicted.
lastSequence	number	yes	Sequence number of the newest event. The UI uses this field to detect new events: if the value has increased relative to the previously stored value, N = lastSequence_new - lastSequence_old new events have been added to the log. Fetching these N events is appropriate only if the current UI page contains the previously stored lastSequence (that is, the user is on the latest page where new entries appear); no updates are needed on other pages.
totalBySeverity	object	yes	Breakdown of total by severity
pendingBySeverity	object	yes	Breakdown of pending by severity

totalBySeverity

Field	Type	Description
debug	number	Number of available DEBUG events
info	number	Number of available INFO events
warning	number	Number of available WARNING events
error	number	Number of available ERROR events
fault	number	Number of available FAULT events

pendingBySeverity

Field	Type	Description
debug	number	Number of pending DEBUG events
info	number	Number of pending INFO events
warning	number	Number of pending WARNING events
error	number	Number of pending ERROR events
fault	number	Number of pending FAULT events