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've came across some really long outputs when debugging. It's also true that I've modified the output by aligning columns to the left to make it a bit more readable. What I would suggest is to remove the Date (not time) information and replace it by every day log, log name would be composed of the removed date.
Consider this is issue more of a TODO/Wish type. Let me know if this is something you would be interested in being done by me.
The text was updated successfully, but these errors were encountered:
I've found the date output useful in the past, especially when looking for log messages around an event that happened a few days prior. Also, if you have multiple server's logs spanning multiple days, you can cat them all together and sort them with the date field, but it wouldn't work without. I guess I'm not sure a configuration option to elide the date would be sufficient: the lines would still be pretty long. To strip out the date, can you just pipe the log through cut -d' ' -f2-?
Long term it'd be cool to have some sort of logging format with sweet tools to process it. But that sounds like a separate project.
I've came across some really long outputs when debugging. It's also true that I've modified the output by aligning columns to the left to make it a bit more readable. What I would suggest is to remove the Date (not time) information and replace it by every day log, log name would be composed of the removed date.
Consider this is issue more of a TODO/Wish type. Let me know if this is something you would be interested in being done by me.
The text was updated successfully, but these errors were encountered: