[Feature]: Implement process-specific log filtering to reduce noise

[gemini44sam-cloud]

Platform

Windows

ProxyBridge Version

3.2

OS and Version

Windows 11 23H2

Documentation

• I have read the Windows documentation
• I have read the macOS documentation
• I have read the Linux documentation

Code Review

• I have gone through the code page

Describe the Feature

Is your feature request related to a problem? Please describe.
Currently, the "Traffic Logging" feature is a global toggle. When debugging specific application proxy behavior, it is nearly impossible to track the requests of the target app because the log UI is overwhelmed by noise from other background processes.

Describe the solution you'd like
I request a granular filtering mechanism in the Traffic Logging UI. Specifically:

Filter by Process Name/PID: A search bar or dropdown in the log window to show logs only from specific applications.

Exclude List: An "Ignore list" for specific processes (e.g., system background services that spam connections), allowing the user to silence unwanted log output.

Describe alternatives you've considered
I've considered disabling global logging, but that prevents me from verifying if my specific proxy rules are correctly applied to the target application.

Additional context
This feature would significantly improve the developer workflow for testing proxy rule accuracy.

Additional Context

[Anof-cyber]

I am not sure use of this feature. Search bar is already there you can search ane filter logs to spepeifc app

[gemini44sam-cloud]

我不確定這個功能的用途。搜尋欄已經存在，你可以搜尋並篩選特定應用程式的日誌。

"The current logging implementation creates an unmanageable 'observation window overflow'. High-frequency processes (like fdm.exe) render the real-time monitoring of targeted applications impossible, as the relevant information is pushed out of the UI buffer before it can be read. Since the logging window is the primary tool for verifying rule efficacy, this behavior effectively breaks the tool's core functionality for advanced users. Searching historical logs is insufficient for real-time rule verification."

[Anof-cyber]

This is available in the beta version #148

Two solutions added for this

1: Ability to disable Log Auto Remove. You can set whether you want ProxyBridge to auto-remove logs or not.
2: You can now set Log Filters to only keep specific logs in the UI. The rest of the logs will be lost. Filter can be based on Process name, IP, Port, Action, and Protocol.