News for hackers. Stuff that matters.
Re:Tips for analyzing logs by lowbloodsugar on Tuesday December 13, 2022 @02:57PM (#33974798)
And you should produce a single line of output for each request that identifies all of the pertinent information. You can have more than one, for e.g. a thread dump, but there should be one that provides a complete summary. I've lived with apps that logged at each stage of the process as separate lines, and that's just not useful data when grepping for anomalies.
Re:Tips for analyzing logs by rsdbdr203 on Tuesday December 13, 2022 @05:08PM (#33976705)
I hypothesize it's not useful because you're using grep. If you use a tool that can show you multiple lines all tied by a request ID, it becomes much more helpful.
Re:Tips for analyzing logs by lowbloodsugar on Tuesday December 13, 2022 @11:04PM (#33979883)
I am quite often looking for patterns across thousands of requests. As an example, one thing I inherited didn’t even log how long each request took to serve. Sure, you find out how long a single request took, by comparing the first and last log entry, but that’s just not useful 99% of the time.
Re:Tips for analyzing logs by pantulis on Wednesday December 14, 2022 @06:04AM (#33982064)
This is exactly the kind of lack of logging info that exasperates any on call person.