Recent log lines from this appliance
const url = 'http://localhost:11044/api/v1/admin/logs?limit=200';const options = {method: 'GET', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}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.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”How many lines, newest last. Clamped to the buffer’s own size.
Only entries at this level or above: ERROR, WARN, INFO, DEBUG, TRACE.
Responses
Section titled “Responses”Recent log entries, oldest first
What GET /admin/logs answers: the most recent events this process holds in memory. Not a container log, and lost on restart
object
How many events the in-memory buffer holds at most (200); asking for more cannot return more
The entries, oldest first, after the level filter
One event this appliance process logged, as a structured line
object
Log level: ERROR, WARN, INFO, DEBUG or TRACE
Simple name of the logger, package stripped — normally the logging class
The formatted message, with the first-run setup token redacted. No stack trace
Name of the thread that logged it
When the event was logged, in epoch milliseconds (UTC)
True when as many entries came back as limit asked for, so older ones may have been cut off
Example generated
{ "bufferSize": 1, "entries": [ { "level": "example", "logger": "example", "message": "example", "thread": "example", "timestamp": 1 } ], "truncated": true}
