You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not quite sure why there is no empty fields in exported logs. For instance, if you don't specify exception / stacktrace it returns empty string. This is bad, since you don't know which part of the logs you are missing. This is required if you want to parse logs on other system, fe. google Stackdriver.
IMO it should return empty {} so we can easily split each row and parse it more easily.
This could be easily configured via cfg file to keep backward compatibility.
So, after over a year, I'm bumping it up :) I have created new PR. Please take a look @zubairehman . It doesn't change default behaviour, it extends it if you configure it in a different way.
I'm not quite sure why there is no empty fields in exported logs. For instance, if you don't specify exception / stacktrace it returns empty string. This is bad, since you don't know which part of the logs you are missing. This is required if you want to parse logs on other system, fe. google Stackdriver.
IMO it should return empty
{}
so we can easily split each row and parse it more easily.This could be easily configured via cfg file to keep backward compatibility.
PR for this created: #21
The text was updated successfully, but these errors were encountered: