Filtering log messages

1

Hi All,

Since I have a backup job on Mega, I receive the log messages:

…[Warning-Duplicati.Library.Main.Controller-MegaUnmaintained]…

I wanted to suppress those messages and did following (in the backup job’s Advanced Options):

  1. Added a console-log-filter: -[.*MegaUnmaintained.*]
  2. Set the console-log-level to Error

But still receive those messages. Any hints please, how to suppress them?
I’m using 2.1.0.110_canary_2025-02-28

2

The warnings are not filtered when logging to the results, so you cannot suppress them, which is quite annoying for a situation like the one you describe.

I have a fix ready for the next canary that adds --suppress-warnings=MegaUnmaintained,OtherId,ThirdId

This will change the warnings to information messages so they do not show up as warnings on the backup run.

3

Where? Yellow popup? Default job log? Log file? Console output from a command line?

Your attempt to configure console is for command line. A log-file has similar options.

Unfortunately I’m wondering if you mean a yellow warning popup, Show log, and job log.

That’s a more annoying situation that the new feature (if I understand it) is meant to help.

If you mean console or log file output, then filters similar to what you have show will work.

4

I meant this warning:

image
image478×196 15.3 KB

5

Hi kenkendk, could you please explain this:

logging to the results

6

Hi ts678,

Actually a good point. I think the nomenclature of all of those listed possibilities shall be more unique. Not only for the developers, but also for the users - but if it is already the case, then sorry that I’m still that blond…

7

How about a functionality for the new UI (but it is welcome for the old one too):

  • Clicking on a warning opens a (context) menu/pop-up with at least this menu on it:
    Ignore this warning class for this job in the future

This would do whatever is necessary not to show (i.e. not even generate) this warning class for this backup job (and also not for warnings it was earlier called for).

Other menu could be setup to show it as info.

image
image903×346 13.5 KB

8

Yes, I see that was a bit opaque.

Internally, the code logs a lot of information, that you can see in the various logs.
When a message is logged with the log level “warning” it is captured by the backup results that can later be reported. The same logic is for log messages with the level “error” where they will be captured as errors.

That is a great idea. I have registered it as an issue.