Diagnostics information in debug output
Hello Folks, I realized that our nice "--diagnostics" output is not integrated by default in BIT. But my opinion is it should be. But the original JSON output (see at the end of this mail) is a bit to much I would say. But I'm not sure. I'm interested in your opinions. For the "--debug" output I would use the log format like this: DEBUG: [...] Diagnostics - "backintime" name: "Back In Time" version: "1.3.3-dev" .... DEBUG: [...] Diagnostics - "host-setup" platform: ... DEBUG: [...] Diagnostics - "python-setup" python: ... sys-path: "/usr/...", "/usr/..." DEBUG: [...] Diagnostics - "external-programs" rsync: ... I assume this can be realized with less code. Any suggestions about it? Here is an example of diagnostic output in JSON format. { "backintime": { "name": "Back In Time", "version": "1.3.3-dev", "latest-config-version": 6, "local-config-file": "/home/UsernameReplaced/.config/backintime/config", "local-config-file-found": true, "global-config-file": "/etc/backintime/config", "global-config-file-found": false, "started-from": "/usr/share/backintime/common", "running-as-root": false, "user-callback": "/home/UsernameReplaced/.config/backintime/user-callback", "keyring-supported": true }, "host-setup": { "platform": "Linux-5.10.0-21-arm64-aarch64-with-glibc2.31", "system": "Linux #1 SMP Debian 5.10.162-1 (2023-01-21)", "os-release": "Debian GNU/Linux 11 (bullseye)", "display-system": "x11", "locale": "de_DE, UTF-8", "PATH": "/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games", "RSYNC_OLD_ARGS": "(not set)", "RSYNC_PROTECT_ARGS": "(not set)" }, "python-setup": { "python": "3.9.2 default Feb 28 2021 17:03:44 CPython GCC 10.2.1 20210110", "python-executable": "/usr/bin/python3", "python-executable-symlink": true, "python-executable-resolved": "/usr/bin/python3.9", "sys.path": [ "/usr/share/backintime/qt/plugins", "/usr/share/backintime/common/plugins", "/usr/share/backintime/plugins", "/usr/share/backintime/common", "/usr/lib/python39.zip", "/usr/lib/python3.9", "/usr/lib/python3.9/lib-dynload", "/usr/local/lib/python3.9/dist-packages", "/usr/lib/python3/dist-packages", "/usr/lib/python3.9/dist-packages" ], "qt": "PyQt 5.15.2 / Qt 5.15.2" }, "external-programs": { "rsync": "3.2.3", "ssh": "OpenSSH_8.4p1 Debian-5+deb11u1, OpenSSL 1.1.1n 15 Mar 2022", "sshfs": "3.7.1", "encfs": "1.9.5", "shell": "/bin/bash", "shell-version": "GNU bash, Version 5.1.4(1)-release (aarch64-unknown-linux-gnu)" } }
On Tue, 2023-03-07 at 15:25 +0000, c.buhtz@posteo.jp wrote:
I realized that our nice "--diagnostics" output is not integrated by default in BIT.
What exactly with "not integrated"? The mix of debug and diagnostics output if --debug and --diagnostics is used together? We could ignore the --debug switch if --diagnostics is used since the only purpose of --diagnostics is to print the JSON output and end BiT.
But the original JSON output (see at the end of this mail) is a bit to much I would say.
I get used to it since I find the required info quite fast. I wouldn't invest time to change this again. What's the cause of your question, are there open issues or user feed-back?
Moin Am 17.03.2023 00:48 schrieb BiT dev:
What exactly with "not integrated"? The mix of debug and diagnostics output if --debug and --diagnostics is used together?
We could ignore the --debug switch if --diagnostics is used
I mean it the other way around. When using "--debug" it always should contain the diagnostics output. Then we don't have to ask for diagnostic output explicit.
participants (2)
-
BiT dev
-
c.buhtz@posteo.jp