Improve logs

[Davidson-Souza]

No description provided.

[Sweetdevil144]

Hi @Davidson-Souza . Is this issue open for the community? I would like to tackle this Issue. Can you describe what specific log types are you trying to target when you say Improve logs?

[Davidson-Souza]

Hi @Sweetdevil144 . Yes, this is open for anyone to grab.

There are a lot of things that can be improved in the current logging system. The messages can be improved to be more clear, the formatting can be less verbose... I was specially thinking about debug logging, with more useful information for digging problems. I would like better tracing log for low-level operations like OS calls and database changes.

So, the first job is probably to figure out what can be improved and made clearer

[leif-runescribe]

Hi, as this issue is related to logging, and a good first issue, I'd like to take it up

[jaoleal]

Do it! @leif-runescribe

[leif-runescribe]

Would you mind specifying which logs require improvements,
I figured maybe i should work on the Floresta cli error logs, but that's not very helpful is it?
As @Davidson-Souza mentioned, should i work on the low level and db related logs?

[jaoleal]

I would recommend to try yourself and propose your opinion for this issue.

• Sometimes floresta starts doing ibd and stops logging. But is doing idb.

• We dont have levels of debugging. all te time logging everything is no good for development and sometimes can waste some precious resources.

• Its verbose

Thins like this and error handling doesnt have a pattern of implementation. We need to discuss some, feel free to propose.

[jaoleal]

I ended up thinking a lot about this issue. I would suggest to use the default log api and define it levels in compile time as this example here...

may this could be solved after #86 would avoid some rework 👍