Debug logging settings

[jakubsuchybio]

For better understanding what is happening. We have crash reports on HockeyApp, but when someone reports some issue, we should be able to request from them debug logs for further analysis.

I would make this in Settings as checkbox to enable Debug Logging.
It would gather debug output into some local file, that could be transfered by issue creator.

Also with this, we should also improve our output logs.
Personally I would make 2 levels of debugging. First that we have now in output window and second, that would be more verbose with more data in it as well. For example:

• Logging every request (without user sensitive info) and response from the server. (Time, status code, type and response data)
• Logging navigation queries (Time, From where, to where)
• Logging every button tapping (Time, on which page, on which button)

Any other ideas what we could include in this Debug logging?

I don't know what we are using now, but I am really great experience with NLog nuget package, where can be set severity levels, multiple streams logging (output and file at the same time), etc.

[ST-Apps]

This is quite easy if you have some spare time: implement ILogger (iirc) and make it save to file instead of printing to console as we're doing now.

[robertmclaws]

I've been thinking about similar logging expansion for 2.0. I don't necessarily think we should have an option in Settings, because not everyone needs to see it. BUT we could put it behind a debug build flag or something.

What I was thinking about was a console window in the app that would let you see the debug output in real-time. Someone else posted the same idea. It could either be backed by a file logger, or the ILogger implementation would just add the debug output to a bindable list of strings.

Ideally, the ILogger implementation would work with the DI system, and let you have multiple loggers plugged in. That way you could log to the Console and Hockey and they wouldn't be mutually-exclusive.

[Migsi]

Might not be the right place to ask, but is this repo dead?