Logging with context

[jmatthewsr-ms]

Any plans to add some context to all log statements, where possible?

Examples:

• for illustration purposes only, realize that prefix log statements would break users who parse the current logs. would need to add to end or flag next-gen logging somehow.

Socket.prototype.disconnect = function () {
if (!this.disconnected) {
this.log.info("'{socketId:' + this.id + '}'",'booting client');

Transport.prototype.onForcedDisconnect = function () {
if (!this.disconnected) {
this.log.info("'{socketId:' + this.socket.id + '}'"'transport end by forced client disconnection');

[3rd-Eden]

This will happen when engine.io is integrated with socket.io as it uses the debug module to allow context based logging

On Saturday, November 3, 2012 at 12:30 AM, Justin Matthews wrote:

Any plans to add some context to all log statements, where possible?
Examples:
for illustration purposes only, realize that prefix log statements would break users who parse the current logs. would need to add to end or flag next-gen logging somehow.

Socket.prototype.disconnect = function () {
if (!this.disconnected) {
this.log.info (http://this.log.info)("'{socketId:' + this.id + '}'",'booting client');
Transport.prototype.onForcedDisconnect = function () {
if (!this.disconnected) {
this.log.info (http://this.log.info)("'{socketId:' + this.socket.id + '}'"'transport end by forced client disconnection');

—
Reply to this email directly or view it on GitHub (#1071).