[bisq-network/bisq] Better logging & exception handling strategy (Discussion #6146)

[xyzmaker123]

Problems:
- support person very often needs to ask user about sending logs - it's quite inconvenient
- logs not always contains enough informations to investigate issue

Objectives:
- consider automation of sending logs (especially errors) to developers - user should allow it in app
- we need to care about privacy - logs shouldn't contains too sensitive data
- logs should contains as much relevant information as possible

Sample bug reports:
- [Missing seeds](https://github.com/bisq-network/bisq/issues/6144)
- [Account signing problem](https://matrix.to/#/!NURMJhBHzBOaaeKira:matrix.org/$TSaxuRuf1UTuhUDZXxdkF0EjKoNGH5gRDUn0EOfbEe4?via=matrix.org&via=matrix.cccgoe.de&via=catgirl.cloud)

References:
- https://stackify.com/java-logging-best-practices/
- https://www.papertrail.com/solution/tips/logging-in-java-best-practices-and-tips/
- https://github.com/payneteasy/slf4j-remote
- https://www.slf4j.org/docs.html

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/discussions/6146
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/repo-discussions/6146 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220412/ee34fa04/attachment.htm>