FR: Separate Logs for each archive

[lamyergeier]

The problem

Is it possible that user can select to have separate log for each archive for each repository separately? The logs can be shown in the archives tab next to the name column. This can make life a bit easier, to troubleshoot, as vorta doesn't support showing separate logs like journalctl, which has advanced log filtering capabilities.

Also, may be the separate logs can be stored next to the repository.

Requested Solution

Described above

Alternatives

GUI for [bit-team/backintime: Back In Time - A simple backup tool for Linux](https://github.com/bit-team/backintime) does this.

Additional context

Its also fine if you want to have a single log file which is available at Misc tab in the GUI. But , also please provide separate log for each archive. Usually one wants to see log for a particular archive (created on a particular date and time) for a particular repository.

[real-yfprojects]

How BiT did can be found in their docs.
BiT implements an own log viewer for that functionality. This could be implemented for vorta too - however not in the near feature, in my opinion, since it is quite the efford.

I think the current system is very straightforward: You open the location of the log files from vorta. Open the correct file in you editor, enter search mode and enter the time of the profile shown in the archive table.

[lamyergeier]

Without implementing much, can we just separate log for each archive and associate each archive with its own log file?

[real-yfprojects]

Without implementing much, can we just separate log for each archive and associate each archive with its own log file?

What about the majority of log entries which cannot be associated to a archive?

[lamyergeier]

May be the logs that are not associated with any archive can go into a common log file like vorta.log

[ThomasWaldmann]

This is definitely something missing.

The Schedule -> Log view on the GUI shows the command, the repository and the rc code, but for rc==1 it is essential to be able to view the detailled logs to decide whether it was a harmless or a harmful warning.

There could be also a button on that view, right besides the return code to open a log view just for that borg run.

Associating the logs with the archive is also a nice idea, but would not fit all kinds of use cases (e.g. if the borg command is not related to one specific archive).

If someone implements this, it could just use a plain text view of the log at first.

Later, a log parser could parse the log and colour the lines according to the log level (DEBUG, INFO, WARNING, ERROR, CRITICAL, ...). There is already code for this in borg-web project.