{"action":"opened","issue":{"url":"https://api.github.com/repos/decred/dcrd/issues/678","repository_url":"https://api.github.com/repos/decred/dcrd","labels_url":"https://api.github.com/repos/decred/dcrd/issues/678/labels{/name}","comments_url":"https://api.github.com/repos/decred/dcrd/issues/678/comments","events_url":"https://api.github.com/repos/decred/dcrd/issues/678/events","html_url":"https://github.com/decred/dcrd/issues/678","id":225455867,"number":678,"title":"Better logger","user":{"login":"jrick","id":1420313,"avatar_url":"https://avatars0.githubusercontent.com/u/1420313?v=3","gravatar_id":"","url":"https://api.github.com/users/jrick","html_url":"https://github.com/jrick","followers_url":"https://api.github.com/users/jrick/followers","following_url":"https://api.github.com/users/jrick/following{/other_user}","gists_url":"https://api.github.com/users/jrick/gists{/gist_id}","starred_url":"https://api.github.com/users/jrick/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jrick/subscriptions","organizations_url":"https://api.github.com/users/jrick/orgs","repos_url":"https://api.github.com/users/jrick/repos","events_url":"https://api.github.com/users/jrick/events{/privacy}","received_events_url":"https://api.github.com/users/jrick/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-05-01T15:32:25Z","updated_at":"2017-05-01T15:32:25Z","closed_at":null,"body":"I'm fed up with seelog and would like all of the tooling to switch over to a better logger.  This brainstorming/tracking issue is being made in the dcrd repo but it really affects all of the go projects.\r\n\r\nHere are some of the problems with seelog:\r\n\r\n* can't log any mutable data, causes data races (format strings are created from the passed data after the call returns)\r\n* async logging and output throttling can cause logs to show up minutes after the fact\r\n* just all round really slow\r\n\r\nBecause of these issues I think it would be wise to switch to a new logger.  Here are some of the hard feature requirements:\r\n\r\n* log levels\r\n* changing log levels at runtime\r\n* subsystems (could be just a prefix added by a particular a logger variable)\r\n* per-subsystem (or per-logger-variable) log levels\r\n* format string API (must be able to drop this in without rewriting every log statement)\r\n\r\nHere are some of the features of seelog that I don't believe are hard requirements.\r\n\r\n* logging to a file (write logs to stdout and use shell redirection, tee, etc. instead)\r\n  * yes, windows can do this too\r\n* log rotation (handled better by other tools, if logs are saved)\r\n* async logging (can still have this without the data races but i find it unnecessary)\r\n\r\nPlease comment regarding what features you think we absolutely need and those we don't.  We should come to a conclusion about our requirements before continuing.  Once requirements have been laid out, we can begin looking for any alternative loggers that meet these requirements or roll our own."}}
{"actor":{"display_login":"jrick"}}