Implement a filter for the Execution Log #11322

New issue

Open

opened 2026-02-21 21:22:36 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 21:22:36 -05:00

Owner

Originally created by @xypha on GitHub (Nov 28, 2020).

Please provide the following information
(Updated 2025.05.25)

qBittorrent version and Operating System

v5.1.0 x64 - windows 11 24H2 - 26100.3476

Extra info(if any)

Feature Request / Enhancement

Execution Log is cluttered.
Current filtering options are limited to below options

Normal
Information
Warning
Critical

Improving filtering options in Execution Log would help a lot!

either in the form of more categories/sub-categories/tags (similar to how torrent categories and tags work) that cover the origin of the messages (a rough example is listed below)
or a text filter that works similar to the Filter torrents... in Top Toolbar
or maybe something entirely different that I am missing, that can help find specific msgs or browse them more easily

Origin of messages in Execution Log (a rough example):

Torrent
- moved / moving / enqueued
- removed
- added
- renamed (not captured in log at present)
- queue change (move up / down / top / bottom - not captured in log at present)
- resumed
- restored
RSS
- removed
- added (new RSS)
- renamed
- updated
- downloading (example - xxx.torrent)
Failed operations / Errors
Other (startup / IP / port / etc.)

Originally created by @xypha on GitHub (Nov 28, 2020). **Please provide the following information** (Updated 2025.05.25) ### qBittorrent version and Operating System v5.1.0 x64 - windows 11 24H2 - 26100.3476 ### Extra info(if any) Feature Request / Enhancement Execution Log is cluttered. Current filtering options are limited to below options - Normal - Information - Warning - Critical Improving filtering options in Execution Log would help a lot! * either in the form of more categories/sub-categories/tags (similar to how torrent categories and tags work) that cover the origin of the messages (a rough example is listed below) * or a text filter that works similar to the `Filter torrents...` in Top Toolbar * or maybe something entirely different that I am missing, that can help find specific msgs or browse them more easily Origin of messages in Execution Log (a rough example): - Torrent + moved / moving / enqueued + removed + added + renamed (not captured in log at present) + queue change (move up / down / top / bottom - not captured in log at present) + resumed + restored - RSS + removed + added (new RSS) + renamed + updated + downloading (example - xxx.torrent) - Failed operations / Errors - Other (startup / IP / port / etc.)

deekerman added the

Feature request

GUI

Filters

labels

2026-02-21 21:22:36 -05:00

deekerman commented

2026-02-21 21:22:45 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**