Out on HF and heard nobody, but didn't call CQ? Nobody heard you either. 73 de N7GH
Les Morgan wrote:I like your format better, and I agree: it is a difference audience that you write for when you do log files--people that read them tend to be more left brain dependent, so more info in a smaller space is better instead of flowery sentences.
Junilu Lacar wrote:You can take it a step further and format all or a subset of your log messages so that they are machine readable. That way, it's easier to automate. You could put a marker on the machine-readable log messages or you could append them to a separate log altogether.
Tim Driven Development | Test until the fear goes away
Junilu Lacar wrote:Not everything that is machine readable has to be in binary format. JSON, for example, is machine readable as well as human readable. It's machine readable because it has a specific format that can be processed programmatically. CSV is another machine readable format. Properties (key=value pairs) are also machine readable. Free formatted prose does not lend itself well to being machine readable with current technology. You'd need to have some kind of natural language parser and interpreter. Maybe IBM Watson will lead us there someday, but I digress. Anyway, I hope that clarifies what I meant.
Tim Cooke wrote:In your other topic about Logging I mentioned that the company I currently work for uses Splunk to capture the logging output from application servers. I also mentioned that it also serves as a pretty darn good data analysis tool too. Well Splunk loves key=value pairs and is really good at finding them quickly, so taking your example I could write a simple search for "sessionId=97fd45ef21225b079967efd" to obtain an audit of everything that occurred during that user session.