{"action":"opened","issue":{"url":"https://api.github.com/repos/opentracing/opentracing.github.io/issues/26","labels_url":"https://api.github.com/repos/opentracing/opentracing.github.io/issues/26/labels{/name}","comments_url":"https://api.github.com/repos/opentracing/opentracing.github.io/issues/26/comments","events_url":"https://api.github.com/repos/opentracing/opentracing.github.io/issues/26/events","html_url":"https://github.com/opentracing/opentracing.github.io/issues/26","id":127029425,"number":26,"title":"Make log an extension or rename it?","user":{"login":"adriancole","id":64215,"avatar_url":"https://avatars.githubusercontent.com/u/64215?v=3","gravatar_id":"","url":"https://api.github.com/users/adriancole","html_url":"https://github.com/adriancole","followers_url":"https://api.github.com/users/adriancole/followers","following_url":"https://api.github.com/users/adriancole/following{/other_user}","gists_url":"https://api.github.com/users/adriancole/gists{/gist_id}","starred_url":"https://api.github.com/users/adriancole/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adriancole/subscriptions","organizations_url":"https://api.github.com/users/adriancole/orgs","repos_url":"https://api.github.com/users/adriancole/repos","events_url":"https://api.github.com/users/adriancole/events{/privacy}","received_events_url":"https://api.github.com/users/adriancole/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-01-16T14:41:37Z","updated_at":"2016-01-16T14:41:37Z","closed_at":null,"body":"Each feature we add to OpenTracing comes at a cost. I feel the logging aspect is the heaviest feature, and also the most curious.\r\n\r\nAt least in Java, almost  all tracing projects I have seen have log  integration through context properties (ex MDC). This allows the systems to be decoupled,  yet allow a query to join them together (ex by span id). It means zipkin doesn't have to also be logs task and visa versa. \r\n\r\nLogging apis are hard to get right and while we have a lot of tracing folks in the room,  we are notably missing the app designers of log apps like SLF4J etc.\r\n\r\nIf we had a better named version of 'annotation' (like event) which had no aspiration to be a logging api,  I'd feel more comfortable. I really  don't want to accidentally  inherit logging responsibilities  and think having logging apis is a slippery  slope to that. \r\n\r\nIOTW Zipkin is already difficult  to sustain  and ancillary minimum  features such as logging  and attachments worry me. Tell me why I shouldn't be! "}}