Databases
StackOverflow2013
Postsdbo
POHow do Winston's log streams work?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do Winston's log streams work?
    primarykey
    data
    text
    <p>The <a href="https://github.com/flatiron/winston" rel="noreferrer">Winston</a> documentation has a section on <a href="https://github.com/flatiron/winston#streaming-logs" rel="noreferrer">streaming logs</a> which says:</p> <blockquote> <p>Streaming allows you to stream your logs back from your chosen transport.</p> </blockquote> <p>and gives the following code example:</p> <pre><code>// // Start at the end. // winston.stream({ start: -1 }).on('log', function(log) { console.log(log); }); </code></pre> <p>My reading of this is that each new log message added would be output to the console. The <code>{start: -1}</code> config tells the stream to start at the end of the file, so only new log entries are output. I expect the following Node script would result in each existing line of the <code>test.log</code> file being output to the console, and then a new object to be output every 500ms thereafter.</p> <pre><code>var winston = require('winston'); winston.add(winston.transports.File, { filename: 'test.log' }); winston.remove(winston.transports.Console); winston.stream().on('log', function(log) { console.log(log); }); setInterval(function(){ winston.log('info', 'help'); }, 500); </code></pre> <p>I would expect to see something like the following output:</p> <pre><code>{"level":"info","message":"help","timestamp":"2013-12-10T05:55:15.806Z"} {"level":"info","message":"help","timestamp":"2013-12-10T05:55:16.307Z"} {"level":"info","message":"help","timestamp":"2013-12-10T05:55:16.809Z"} {"level":"info","message":"help","timestamp":"2013-12-10T05:55:17.309Z"} {"level":"info","message":"help","timestamp":"2013-12-10T05:56:48.316Z"} </code></pre> <p>What actually occurs is that the logging works as expected with the File transport (the file gets a new log entry every 500ms) but there is no output to the console. The <code>console.log(log)</code> line is never called. </p> <p>Have I missed something obvious, or misunderstood the purpose of Winston's log streams? </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTom
    1. USdrzax
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POHow do Winston's log streams work?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow do Winston's log streams work?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COmaybe they use the conventional `'data'` event?
      singulars
      1. POHow do Winston's log streams work?
      1. USbevacqua
    2. COI've had the same issue, and I suspect it doesn't work with File or Console transports as these are the two I've tried, and the callback never gets called. @Nico, This code is directly from the README of winston and in the code: out.emit('log', log); The problem is, that nothing I have tried seems to make this work :(
      singulars
      1. POHow do Winston's log streams work?
      1. USRobin Duckett
    3. COThanks for confirming my suspicions @RobinDuckett. I'd file this as a bug, but Winston looks more or less dead: https://github.com/flatiron/winston/issues/294 Might need to fork.
      singulars
      1. POHow do Winston's log streams work?
      1. USdrzax
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload