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.

Opening an API request on the Traces page shows the request as its own page, at /app/traces/<id>: the status, the error LocalAI recorded, a timeline with the backend operations that ran while the request was open, and the request and response bodies. Bodies stay closed until revealed, and request headers are not listed. See Traffic.