Interactive and asynchronous logging tool for Node.js. An easier way to log & debug complex requests directly from the command line. Still experimental !

investigator uses a node based logging system. Log nodes (agents) can be nested to help organizing the different steps, synchronous or not, of the process. An agent is defined by its name and can be retrieved at any time in the scope of its parent agent.

import {agent} from 'investigator';

const requestAgent = agent('request');
const getUserAgent = requestAgent.child('getUser')
  .log('Retrieving user from db...');

// ...

getUserAgent.success('Done !');
// Or: requestAgent.child('getUser').success('Done !');

async agents are particular nodes which may be resolved or rejected to provide a feedback of their fulfillment.

import {agent} from 'investigator';

const requestAgent = agent('request');

// Creates an async child agent
const getUserAgent = requestAgent.async('getUser')
  .log('Retrieving user from db...');

myAsynchronousFunction().then(() => {
  getUserAgent.resolve('Done !');
}).catch((err) => {
  getUserAgent.reject(err);
});

investigator provides an inspector module to allow deep object logging directly in the command line interface, like a browser devtools inspector. It also displays the current stack trace of each log.

Use npm install investigator to install locally. See Usage and API Reference for more information.

In the command line interface, the following shortcuts are available:

• Scroll up and down with up arrow, down arrow, or mouse wheel. You may also click on a row to select it.
• Open Inspector with i (inspect the currently selected row).
• Scroll to bottom with b
• Enable auto-scroll with s. Disable by pressing an arrow key.

Clone the project with git clone [email protected]:risq/investigator.git.

Install dependencies with npm install.

Launch the example with node examples/index.js.

You can build the project (transpiling to ES5) with npm run build.

• Log as traditional console.log (or use a multi-transport logging lib like winston), then parse output stream in real time (or from a log file) with investigator.
• Improve UI, navigation & controls in the CLI.
• Add some performance monitoring.
• Improve CLI performance for long time logging (avoid memory leaks).
• Allow client-side logging via WebSockets.

Creates a new root agent, with a given name. Data parameters of any type can also be passed to be logged into the command line interface.

import {agent} from 'investigator';

onRequest(req, res) {
  const requestAgent = agent('request', req.id, req.url);
}

Log passed data parameters under the given agent node. Returns the same agent (so it can be chained).

import {agent} from 'investigator';

onRequest(req, res) {
  const requestAgent = agent('request', req.id, req.url);
  requestAgent.log('Hello')
    .log('World');
}

Log passed data parameters under the given agent node, as a success (displayed in green). Returns the same agent (so it can be chained).

Log passed data parameters under the given agent node, as a warning (displayed in yellow). Returns the same agent (so it can be chained).

Log passed data parameters under the given agent node, as an error (displayed in red). Returns the same agent (so it can be chained).

Returns a child of the current agent, defined by its name. If a child with the given name already exists on the agent, it will be returned. If not, it will be created.

Data objects can be passed as parameters and will be logged on the child's context.

import {agent} from 'investigator';

onRequest(req, res) {
  const requestAgent = agent('request', req.id, req.url);

  if (req.url === '/user/login') {
    requestAgent.child('login', 'Logging in...');

    if (validate(req.user, req.password)) {
      requestAgent.child('login')
        .success('Login data validated !');
    } else {
      requestAgent.child('login')
        .error('Error validating user data.')
    }
  }
}

Returns a asynchronous child of the current agent, defined by its name. If a child with the given name already exists on the agent, it will be returned. If not, it will be created.

Data objects can be passed as parameters and will be logged on the child's context.

An async agent has .resolve() and .reject() methods, to keep track of its fulfillment.

import {agent} from 'investigator';

onRequest(req, res) {
  const requestAgent = agent('request', req.id, req.url);

  if (req.url === '/user/login') {
    requestAgent.child('login', 'Logging in...');

    authUser(req.user, req.password).then(() => {
      requestAgent.child('login')
        .success('Authentication succeeded !');
    }).catch((err) => {
      requestAgent.child('login')
        .error('Error validating user data.')
    });
  }
}

Resolves an async agent. Log data parameters under the given agent node, as a success. Returns the same agent (so it can be chained).

An async agent can only be resolved or rejected once.

Resolves an async agent. Log data parameters under the given agent node, as an error. Returns the same agent (so it can be chained).

An async agent can only be resolved or rejected once.

Feel free to contribute ! Issues and pull requests are highly welcomed and appreciated.

The MIT License (MIT)

Copyright (c) 2015 Valentin Ledrapier

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.