| |||||||||||||
They should be paying attention to the lumberjack projectThey should be paying attention to the lumberjack projectPosted Apr 17, 2012 16:46 UTC (Tue) by k8to (subscriber, #15413)In reply to: They should be paying attention to the lumberjack project by dlang Parent article: Toward more reliable logging
Well, this is more about generating useful log messages, which is the application side. Handling those messages reasonably is the featureset you're referring to.
Although I think handling/transferring is really just the basic work, and where we are headed is to searching/reporting/alerting. Good logs and a good infrastructure that you feed them to can give you a very large amount of knowledge about your systems relatively easily.
(Log in to post comments)
They should be paying attention to the lumberjack project Posted Apr 17, 2012 19:00 UTC (Tue) by dlang (✭ supporter ✭, #313) [Link]
Things work better if everyone generating structured messages use the same structure, otherwise you end up having to use heuristics to guess which structure the incoming log is in, and that path leads us right back the the current mess where every app (and frequently every log message in every app) defines it's own 'structure'.
|
|||||||||||||