Skip to content

Log exclude regex is not applied unless an exclude keyword is set #1284

@x15rte

Description

@x15rte

Operating system

Windows

System version

25H2

Installation type

zip

Version

1.1.0

Description

If I only use Log exclude regex and leave Log exclude keyword empty, the regex is not applied and matching lines are still shown in the log window.
Example lines I want to hide:

ERROR[...] connection: connection upload closed: raw-read tcp4 172.19.0.1:55555->172.19.0.2:66666: An existing connection was forcibly closed by the remote host.

Enable exclude: enabled
Log exclude keyword: empty
Log exclude regex:

connection: connection upload closed: raw-read tcp4 .*An existing connection was forcibly closed by the remote host\.

With this setup, these lines are still printed.

If I add any dummy text in Log exclude keyword (for example DUMMY), then the same regex starts to work and the lines are hidden.

So it looks like Log exclude regex only works when there is at least one exclude keyword set, which is confusing.

Reproduction

Open Basic Settings → Logging.
Enable Log exclude.
Leave Log exclude keyword empty.
In Log exclude regex, add a pattern that matches some log lines

Apply and run a profile until such a line appears.
The line is still visible (regex not applied).

Now go back and add any text to Log exclude keyword (for example DUMMY), keep the same regex.
Run again: the same line is now hidden.

Expected: regex-based exclude should work even when the keyword list is empty.
Actual: regex-based exclude only works when there is at least one exclude keyword.

Logs

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions