mirror of
https://github.com/mudler/LocalAI.git
synced 2026-09-13 06:45:26 -04:00
localai-org-maint-botandlocalai-org-maint-bot
9f62401fca
Register JSON API exchanges before their handlers run so the traces dashboard can surface active work. Replace the live entry with the completed persisted record under the same ID, and clean it up if a handler panics. Assisted-by: Codex:gpt-5 Co-authored-by: localai-org-maint-bot <306269227+localai-org-maint-bot@users.noreply.github.com>
25 lines
1.0 KiB
Markdown
25 lines
1.0 KiB
Markdown
+++
|
|
disableToc = false
|
|
title = "Tracing"
|
|
weight = 83
|
|
url = '/features/tracing'
|
|
+++
|
|
|
|
LocalAI can retain recent API exchanges and backend operations for inspection
|
|
on the **Traces** page in the management interface. Enable tracing in runtime
|
|
settings or with the existing tracing configuration.
|
|
|
|
API requests appear while they are still running. Their elapsed duration
|
|
updates when the page refreshes, and the result column marks them as in
|
|
progress until the response completes. In-flight requests live only in memory;
|
|
the completed exchange is what LocalAI adds to the bounded, persistent history.
|
|
|
|
API and backend trace histories are persisted in separate directories below
|
|
the configured data path. They are restored after a clean service restart,
|
|
whether or not authentication is enabled.
|
|
|
|
Each history remains independently bounded by `tracing_max_items`. When a
|
|
history reaches that limit, LocalAI removes its oldest records from memory and
|
|
disk. The existing clear actions on the Traces page remove both the in-memory
|
|
history and its persisted records.
|