Logging - Arupa Documentation

The Log capability manages the [Log] table described in Logging — Level and Format. All endpoints on this page require the Log capability to be enabled; see Management API for how capabilities work.

Log level

GET /api/log/level
PATCH /api/log/level
Content-Type: application/json

{"level":"debug"}

GET returns the currently configured level. PATCH requires level and writes it to [Log].Level.

{
  "success": true,
  "message": "Log level updated",
  "data": { "level": "debug", "requires_restart": true }
}

Log format

GET /api/log/format
PATCH /api/log/format
Content-Type: application/json

{"format":"text"}

GET returns the currently configured format. PATCH requires format and writes it to [Log].Format.

{
  "success": true,
  "message": "Log format updated",
  "data": { "format": "text", "requires_restart": true }
}

Requires-restart

The Kernel’s logger is built once at startup from whatever [Log] contained at that time. Both endpoints compare the configured value against the one the running process actually applied (case-insensitively) and report the difference as requires_restart. This shows up on a plain GET too, not just right after a PATCH — if someone edited config.toml directly and reloaded, GET /api/log/level already reports requires_restart: true before any API call changes anything. It goes back to false once the configured value matches what’s applied again, whether that’s from restarting the Kernel or from writing the previous value back.

​Log level

​Log format

​Requires-restart

Log level

Log format

Requires-restart