{"action":"created","issue":{"url":"https://api.github.com/repos/pivotal-golang/lager/issues/4","repository_url":"https://api.github.com/repos/pivotal-golang/lager","labels_url":"https://api.github.com/repos/pivotal-golang/lager/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/pivotal-golang/lager/issues/4/comments","events_url":"https://api.github.com/repos/pivotal-golang/lager/issues/4/events","html_url":"https://github.com/pivotal-golang/lager/issues/4","id":40808380,"number":4,"title":"Improve usability of levelled logging","user":{"login":"glyn","id":94953,"avatar_url":"https://avatars.githubusercontent.com/u/94953?v=3","gravatar_id":"","url":"https://api.github.com/users/glyn","html_url":"https://github.com/glyn","followers_url":"https://api.github.com/users/glyn/followers","following_url":"https://api.github.com/users/glyn/following{/other_user}","gists_url":"https://api.github.com/users/glyn/gists{/gist_id}","starred_url":"https://api.github.com/users/glyn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/glyn/subscriptions","organizations_url":"https://api.github.com/users/glyn/orgs","repos_url":"https://api.github.com/users/glyn/repos","events_url":"https://api.github.com/users/glyn/events{/privacy}","received_events_url":"https://api.github.com/users/glyn/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2014-08-21T14:13:58Z","updated_at":"2016-03-15T09:48:41Z","closed_at":"2016-03-15T00:36:12Z","body":"The readme mentions logging levels but only in terms of creating logs. It does not describe how to configure logging at runtime such that only logs of particular levels are output. Without this ability, levels are not so useful. For example, if there are many debug logs, informational messages can be swamped and so it is usual to turn off debug (and possibly info) messages when using a levelled logging system unless debugging is required.\r\n\r\nThen when the logging level needs to be increased, e.g. during debugging, turning on debug logging globally often produces too great a volume of logs, so it is usual in logging systems to be able to narrow down the areas of code for which logging is activated.\r\n\r\nSee, for example, the way the `vmodule` flag of the [glog library](http://godoc.org/github.com/golang/glog) works.\r\n\r\nFor more general inspiration from a mature logging framework, see Java's [logback](http://logback.qos.ch/manual/index.html)."},"comment":{"url":"https://api.github.com/repos/pivotal-golang/lager/issues/comments/196745169","html_url":"https://github.com/pivotal-golang/lager/issues/4#issuecomment-196745169","issue_url":"https://api.github.com/repos/pivotal-golang/lager/issues/4","id":196745169,"user":{"login":"glyn","id":94953,"avatar_url":"https://avatars.githubusercontent.com/u/94953?v=3","gravatar_id":"","url":"https://api.github.com/users/glyn","html_url":"https://github.com/glyn","followers_url":"https://api.github.com/users/glyn/followers","following_url":"https://api.github.com/users/glyn/following{/other_user}","gists_url":"https://api.github.com/users/glyn/gists{/gist_id}","starred_url":"https://api.github.com/users/glyn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/glyn/subscriptions","organizations_url":"https://api.github.com/users/glyn/orgs","repos_url":"https://api.github.com/users/glyn/repos","events_url":"https://api.github.com/users/glyn/events{/privacy}","received_events_url":"https://api.github.com/users/glyn/received_events","type":"User","site_admin":false},"created_at":"2016-03-15T09:48:41Z","updated_at":"2016-03-15T09:48:41Z","body":"Not sure why this was closed."}}