Skip to content

Recent log lines from this appliance

GET
/api/v1/admin/logs
curl --request GET \
--url 'http://localhost:11044/api/v1/admin/logs?limit=200' \
--header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'

The last N events this process logged, newest last. In-memory and bounded — not a container log, and not a history that survives a restart.

limit
integer format: int32
default: 200

How many lines, newest last. Clamped to the buffer’s own size.

level
string

Only entries at this level or above: ERROR, WARN, INFO, DEBUG, TRACE.

Recent log entries, oldest first

Media typeapplication/json

What GET /admin/logs answers: the most recent events this process holds in memory. Not a container log, and lost on restart

object
bufferSize
required

How many events the in-memory buffer holds at most (200); asking for more cannot return more

integer format: int32
entries
required

The entries, oldest first, after the level filter

Array<object>

One event this appliance process logged, as a structured line

object
level
required

Log level: ERROR, WARN, INFO, DEBUG or TRACE

string
logger
required

Simple name of the logger, package stripped — normally the logging class

string
message
required

The formatted message, with the first-run setup token redacted. No stack trace

string
thread
required

Name of the thread that logged it

string
timestamp
required

When the event was logged, in epoch milliseconds (UTC)

integer format: int64
truncated
required

True when as many entries came back as limit asked for, so older ones may have been cut off

boolean

Example generated

{
"bufferSize": 1,
"entries": [
{
"level": "example",
"logger": "example",
"message": "example",
"thread": "example",
"timestamp": 1
}
],
"truncated": true
}