{"action":"opened","issue":{"url":"https://api.github.com/repos/SOHU-Co/kafka-node/issues/229","labels_url":"https://api.github.com/repos/SOHU-Co/kafka-node/issues/229/labels{/name}","comments_url":"https://api.github.com/repos/SOHU-Co/kafka-node/issues/229/comments","events_url":"https://api.github.com/repos/SOHU-Co/kafka-node/issues/229/events","html_url":"https://github.com/SOHU-Co/kafka-node/issues/229","id":99488127,"number":229,"title":"Instrumentation for kafka-node client: Improvement","user":{"login":"BadLambdaJamma","id":6640372,"avatar_url":"https://avatars.githubusercontent.com/u/6640372?v=3","gravatar_id":"","url":"https://api.github.com/users/BadLambdaJamma","html_url":"https://github.com/BadLambdaJamma","followers_url":"https://api.github.com/users/BadLambdaJamma/followers","following_url":"https://api.github.com/users/BadLambdaJamma/following{/other_user}","gists_url":"https://api.github.com/users/BadLambdaJamma/gists{/gist_id}","starred_url":"https://api.github.com/users/BadLambdaJamma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BadLambdaJamma/subscriptions","organizations_url":"https://api.github.com/users/BadLambdaJamma/orgs","repos_url":"https://api.github.com/users/BadLambdaJamma/repos","events_url":"https://api.github.com/users/BadLambdaJamma/events{/privacy}","received_events_url":"https://api.github.com/users/BadLambdaJamma/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-06T17:38:09Z","updated_at":"2015-08-06T17:38:09Z","closed_at":null,"body":"We use the kafka-node client in production without any hitches.  However when our developers use this NPM on their various VMs,  and bare metal OSX installations, some very weird behavior can occur specifically with OSX changing the host name when the preferred network connection changes post kafka client connections to the brokers.  Likewise before we got smart about configuring kafka and coding against kafka-node we had many issues  (of our own doing).  These issues required us to single step debugging the kafka-node client sources to solve the problem .  I would like to suggest a new event to be raised by the kafka-node client called on('instrumentation'). The kafka-node client would raise this event with instrumentation information.  Consumers could log the event or simply use it to debug configurations without resorting to stepping sources.\r\n\r\nI would be happy to implement this for the client.js if you think that it is a good idea.  I could have a pull request ready about 2 days after you approve of this idea."}}