mirror of
https://github.com/mudler/LocalAI.git
synced 2026-08-01 02:49:51 -04:00
1189c6825b
* feat(tracing): persist bounded trace histories Retain API and backend traces below the data path, restore them at initialization, and serialize clears with asynchronous consumers. Assisted-by: Codex:gpt-5 * fix(tracing): satisfy persistence security checks Document why persisted filenames cannot escape the trace directory and explicitly ignore the best-effort temporary-file cleanup result. Assisted-by: Codex:gpt-5 [golangci-lint] --------- Co-authored-by: localai-org-maint-bot <306269227+localai-org-maint-bot@users.noreply.github.com>
20 lines
754 B
Markdown
20 lines
754 B
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 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.
|