Repository navigation
Logs viewer: more detail and history for troubleshooting searches, downloads, and post-processing #1007
Description
Describe the request
The Settings → Logs page is a big help (the Warning/Info/Debug dial, the view filter, copy). When I'm trying to figure out why an issue wasn't found or didn't import, though, I still end up in the container's log files. Things that would let me stay in the app:
- A level beyond Debug, or per-area debug toggles (search/indexers, DDL, download clients, post-processing, metadata), so I can turn up detail for the part I'm chasing without flooding the whole log
- Text search and filtering by series/issue, provider/indexer, or component, on top of the severity filter
- Older history: read the rotated files too, or download the full log/archive from the page. Right now it only reads the current
comicarr.log(max 5,000 lines), so after a rotation the lines I need are gone - More context in the log lines themselves: for each search, which providers/indexers were tried with what query, how many results came back, and why each candidate was rejected; for downloads, each DDL/client step and its result; for post-processing, the source path, destination path, and the step that failed, with the full error
- Optional: from an issue's page, a link to its recent activity/log lines
How did you come up with the idea?
I troubleshoot grabs that fail or never import (DDL lookups with no results, post-processing permission errors) and always need more context than the Info level shows, plus history from before the last rotation.
Environment
- Comicarr version: 0.41.4
- Install method: Docker (compose)
- OS: ZimaOS
- Branch / commit: n/a
Additional information
Builds on #611 / #617 (log level dial and Settings log viewer) and relates to #957 (search loop log volume). Per-area verbosity would also help with the volume problem in #957.
Activity
frankieramirez commentedon Oct 8, 2026
Agent Brief
Category: enhancement
Summary: Extend Settings → Logs with retained history, focused finding/export and consistent troubleshooting context.
Current behavior:
get_recent_logs(ctx, lines)deliberately exposes only the currentcomicarr.log, capped at 5,000 lines. The viewer already offers severity filtering, Copy, Refresh, rotation and saved/effective/restart level context. Both old/current log formats and multiline traceback severity are supported. #957's bounded INFO search summary is already implemented; the remaining request is not. Rotated-file access was deferred from #617's first cut, not rejected. No matching.out-of-scope/record exists.Desired behavior and delegated decisions:
CONTEXT.mdanddocs/architecture/logging-levels.md. No fourth level or per-subsystem capture toggles.EvaluationSessionresults already consumed by the workflow. Diagnostics must not consume extra candidates, re-query providers, change selection/pack claims or guess totals.Key interfaces:
get_recent_logs(ctx, lines)and authenticated system log routes: extend with selected retained source and filter scope while preserving current callers.LogsTab/useLogs/logLines: file selection, literal/component/severity filters, multiline rendering, Copy and export.redact_sensitive_text(): common server redaction for historical as well as current output.EvaluationSession.evaluate()/ public candidate verdict: observational diagnostics only.postprocessing.run()and download execution failure boundaries: contextual exception logging.Acceptance criteria:
npm run lintpass; add a changeset and update current-file-only log API documentation.Verification: Source inspection confirms current-tail-only behavior and missing viewer find/history/export. Existing Debug logging covers some requested details but failure context is inconsistent;
postprocessing.run()logs an exception string without a traceback. This enhancement has not been tested against a live container.Out of scope:
frankieramirez commentedon Oct 8, 2026
Split into four sub-issues so each lands as its own reviewable PR:
ready-for-agent, and a good first PR.ready-for-agent.ready-for-agent.needs-info: it needs an exact line shape, the read-only observation point inEvaluationSession, and a real diagnosis that failed for lack of a specific field. It is blocked by Logs viewer: search current and retained log files by text, component and severity #1015 so the format can be checked against real searches.This issue stays open as the parent and no longer carries
ready-for-agent.