Comments on: The trouble with logging http://blog.amber.org/2008/11/02/the-trouble-with-logging/ Thoughts of a minor lunatic Wed, 21 Oct 2009 01:55:36 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Fixing Logging (Pt. 2) - Message Catalogs at Pensieri di un lunatico minore http://blog.amber.org/2008/11/02/the-trouble-with-logging/comment-page-1/#comment-52547 Fixing Logging (Pt. 2) - Message Catalogs at Pensieri di un lunatico minore Fri, 07 Nov 2008 19:22:56 +0000 http://blog.amber.org/2008/11/02/the-trouble-with-logging-in-python/#comment-52547 [...] earlier posts, I ranted about the state of logging and made some observations about who the audience might be. Now I want to talk about something [...] [...] earlier posts, I ranted about the state of logging and made some observations about who the audience might be. Now I want to talk about something [...]

]]> By: petrilli http://blog.amber.org/2008/11/02/the-trouble-with-logging/comment-page-1/#comment-52520 petrilli Mon, 03 Nov 2008 20:44:28 +0000 http://blog.amber.org/2008/11/02/the-trouble-with-logging-in-python/#comment-52520 That's no doubt true, but regardless, whether it be English, French or even Hindi, it's necessary to understand your audience and in many cases, the reduction of narrative also reduces the need to internationalize logging messages. That’s no doubt true, but regardless, whether it be English, French or even Hindi, it’s necessary to understand your audience and in many cases, the reduction of narrative also reduces the need to internationalize logging messages.

]]> By: Matt Doar http://blog.amber.org/2008/11/02/the-trouble-with-logging/comment-page-1/#comment-52519 Matt Doar Mon, 03 Nov 2008 20:22:57 +0000 http://blog.amber.org/2008/11/02/the-trouble-with-logging-in-python/#comment-52519 Some log messages have to be recorded in a way so that the app can be internationalized - your ops admins may not read English Some log messages have to be recorded in a way so that the app can be internationalized – your ops admins may not read English

]]> By: Fixing logging (pt 1) - know your audience at Pensieri di un lunatico minore http://blog.amber.org/2008/11/02/the-trouble-with-logging/comment-page-1/#comment-52517 Fixing logging (pt 1) - know your audience at Pensieri di un lunatico minore Mon, 03 Nov 2008 15:23:23 +0000 http://blog.amber.org/2008/11/02/the-trouble-with-logging-in-python/#comment-52517 [...] my opening rant on the subject of logging, I mentioned that “logging is not tracing is not narrative”, [...] [...] my opening rant on the subject of logging, I mentioned that “logging is not tracing is not narrative”, [...]

]]> By: petrilli http://blog.amber.org/2008/11/02/the-trouble-with-logging/comment-page-1/#comment-52516 petrilli Mon, 03 Nov 2008 12:05:38 +0000 http://blog.amber.org/2008/11/02/the-trouble-with-logging-in-python/#comment-52516 I need to finish the thoughts in this one, as it was late, but I do have some ideas about how to handle it. Strangely, a lot of it comes from times I spent on weird mainframeish systems in the past. I am not, however, arguing for a return to the book cases full of messages, though that's better than what we have today. I need to finish the thoughts in this one, as it was late, but I do have some ideas about how to handle it. Strangely, a lot of it comes from times I spent on weird mainframeish systems in the past. I am not, however, arguing for a return to the book cases full of messages, though that’s better than what we have today.

]]> By: Paul Wilson http://blog.amber.org/2008/11/02/the-trouble-with-logging/comment-page-1/#comment-52513 Paul Wilson Mon, 03 Nov 2008 09:43:51 +0000 http://blog.amber.org/2008/11/02/the-trouble-with-logging-in-python/#comment-52513 In my hobbie project I'm writting logs in the human readible data serialization format 'YAML'. It can be colourised by vim, is indented nicely, is human readible and is parsible by any popular programming (providing the appropriate YAML library is installed). Not sure how it's going to work out, but just a thought. It is the intention that analysis and monitoring tools will be built around the logging format later on, and I hope this system will make this very easy indeed. In my hobbie project I’m writting logs in the human readible data serialization format ‘YAML’. It can be colourised by vim, is indented nicely, is human readible and is parsible by any popular programming (providing the appropriate YAML library is installed). Not sure how it’s going to work out, but just a thought.

It is the intention that analysis and monitoring tools will be built around the logging format later on, and I hope this system will make this very easy indeed.

]]> By: Michael Nygard http://blog.amber.org/2008/11/02/the-trouble-with-logging/comment-page-1/#comment-52512 Michael Nygard Mon, 03 Nov 2008 07:25:31 +0000 http://blog.amber.org/2008/11/02/the-trouble-with-logging-in-python/#comment-52512 In my book, "Release It!", I have a lot to say about logging, along very similar lines. Most developers write log messages as though they, the developers, are the audience for the logs. They aren't. The true audience for logs is either a) operations staff, or b) monitoring systems. Neither of them are going to know the internal structure of the code, so logs shouldn't reflect a conversation between the code and the developer. Instead, logs should be written to inform operations and, particularly, to trigger actions when intervention is needed. Anything logged as "Error" or "Severe" level should mean that a Sev 1 ticket needs to be opened and Incident Management should begin. In my book, “Release It!”, I have a lot to say about logging, along very similar lines. Most developers write log messages as though they, the developers, are the audience for the logs. They aren’t.

The true audience for logs is either a) operations staff, or b) monitoring systems. Neither of them are going to know the internal structure of the code, so logs shouldn’t reflect a conversation between the code and the developer.

Instead, logs should be written to inform operations and, particularly, to trigger actions when intervention is needed. Anything logged as “Error” or “Severe” level should mean that a Sev 1 ticket needs to be opened and Incident Management should begin.

]]>