Add field for consequence

[kenhov]

Something I have realized when working with logging, is that information about consequence is important. When we log an exception, it is nice to know what has happened, but even more important is what is the consequence of this error. Do we loose data? Do we need to update something manually? Will this cause lost revenue?
It would be great to be able to add consequence in the log entry, like .setConsequence("some info").

[jongpie]

Hi @kenhov - for this idea, would you only use this when logging errors/exceptions? Or would there be a benefit to using this for non-errors too?

[kenhov]

I would think this would fit best for errors/exceptions, but I would not mind to have it for the other log levels. Now during the first week of using Nebula logger, I also discovered that the snapshot of the code could be used to just add a comment of the consequence there, and it would be easy to see in the logentry page.