Winston for application logging in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Winston in the context of Express applications?

Winston is a logging library for Node.js and Express apps. It helps record messages about app activity, errors, and other events in a simple and organized way.

beginner

How do you create a basic Winston logger?

You create a Winston logger by importing winston and calling winston.createLogger() with options like log level and transports (where logs go).

beginner

What is a transport in Winston?

A transport is a storage or output for logs, like the console or a file. Winston can send logs to many transports at once.

beginner

Why use different log levels in Winston?

Log levels help organize messages by importance, like 'error' for problems and 'info' for normal messages. This helps find issues faster.

beginner

How can Winston improve debugging in Express apps?

Winston records detailed logs about app events and errors. This helps developers see what happened and fix problems quickly.

What is the main purpose of Winston in an Express app?

A To log application events and errors

B To manage database connections

C To handle HTTP requests

D To serve static files

Winston is used to log events and errors, helping track app behavior.

Which of these is a Winston transport?

A Console

B Router

C Middleware

D Session

Console is a transport that outputs logs to the terminal.

How do you set the log level in Winston?

A By changing environment variables only

B By calling logger.setLevel() method

C By specifying 'level' in createLogger options

D By editing the package.json file

The 'level' option in createLogger defines the minimum log level to record.

What log level should you use for unexpected errors?

A info

B error

C warn

D debug

'error' level is used for serious problems that need attention.

Can Winston send logs to multiple places at once?

A No, only one transport is allowed

B Only if using a plugin

C Only in development mode

D Yes, by adding multiple transports

Winston supports multiple transports to send logs to different outputs simultaneously.

Explain how to set up Winston for logging in an Express application.

Think about how you tell Winston where to send logs and what to record.

Describe the benefits of using different log levels in Winston.

Consider how sorting messages helps when you have many logs.

Practice

1. What is the main purpose of using Winston in an Express application?

easy

A. To connect the app to a database

B. To save and manage logs about the app's actions and errors

C. To handle HTTP requests and responses

D. To style the user interface

Solution

1. Step 1: Understand Winston's role

   Winston is a logging library used to record messages about what the app is doing or errors it encounters.

2. Step 2: Compare with other options

   Handling HTTP, database connections, or UI styling are not related to logging.

3. Final Answer:

   To save and manage logs about the app's actions and errors -> Option B

4. Quick Check:

   Winston logs app events = C [OK]

Hint: Winston is for logging, not for handling requests or UI [OK]

Common Mistakes:

• Confusing logging with request handling
• Thinking Winston manages databases
• Assuming Winston styles the app

2. Which of the following is the correct way to create a Winston logger that logs to the console?

easy

A. const logger = winston.logToConsole();

B. const logger = winston.createLogger(console);

C. const logger = winston.createLogger({ transports: [new winston.transports.Console()] });

D. const logger = new winston.ConsoleLogger();

Solution

1. Step 1: Recall Winston logger creation syntax

   Winston uses createLogger with a transports array specifying where to send logs.

2. Step 2: Identify correct transport usage

   Using new winston.transports.Console() inside transports array is the correct way.

3. Final Answer:

   const logger = winston.createLogger({ transports: [new winston.transports.Console()] }); -> Option C

4. Quick Check:

   Logger with Console transport = D [OK]

Hint: Use createLogger with transports array for console logging [OK]

Common Mistakes:

• Passing console directly instead of transport object
• Using non-existent Winston methods
• Incorrect instantiation of logger

3. Given the following code snippet, what will be the output in the console?

const winston = require('winston');
const logger = winston.createLogger({
  level: 'warn',
  transports: [new winston.transports.Console()]
});
logger.info('Info message');
logger.warn('Warning message');
logger.error('Error message');

medium

A. [Info message]

B. [Info message]\n[Warning message]\n[Error message]

C. [Error message]

D. [Warning message]\n[Error message]

Solution

1. Step 1: Understand log level filtering

   The logger level is set to 'warn', so it logs messages with level 'warn' and higher (warn, error).

2. Step 2: Check which messages are logged

   'info' is below 'warn' so it is ignored; 'warn' and 'error' messages appear in console.

3. Final Answer:

   [Warning message]\n[Error message] -> Option D

4. Quick Check:

   Level 'warn' logs warn and error only = A [OK]

Hint: Logger level filters out lower priority messages [OK]

Common Mistakes:

• Expecting info messages to appear at warn level
• Confusing log levels order
• Ignoring that error is higher than warn

4. You wrote this Winston logger setup but no logs appear in the console:

const logger = winston.createLogger({
  transports: [new winston.transports.Console()]
});
logger.debug('Test log');

What is the most likely reason?

medium

A. The default log level is 'info', so 'debug' messages are ignored

B. Console transport is not supported in Winston

C. You must call logger.start() before logging

D. The logger variable is not declared properly

Solution

1. Step 1: Check default log level behavior

   Winston's default log level is 'info', which logs 'info' and higher severity levels ('warn', 'error'), ignoring lower levels like 'debug'.

2. Step 2: Verify other options

   Console transport is valid; no start() method exists; logger is declared correctly.

3. Final Answer:

   The default log level is 'info', so 'debug' messages are ignored -> Option A

4. Quick Check:

   Default level blocks lower logs = A [OK]

Hint: Set log level to 'debug' to see debug logs [OK]

Common Mistakes:

• Assuming console transport is invalid
• Looking for non-existent start method
• Ignoring default log level filtering

5. You want to log errors to a file named 'error.log' and all logs to the console in an Express app using Winston. Which configuration correctly achieves this?

hard

A. const logger = winston.createLogger({ transports: [new winston.transports.Console(), new winston.transports.File({ filename: 'error.log', level: 'error' })] });

B. const logger = winston.createLogger({ transports: [new winston.transports.File({ filename: 'error.log' }), new winston.transports.Console({ level: 'error' })] });

C. const logger = winston.createLogger({ transports: [new winston.transports.Console({ level: 'error' }), new winston.transports.File({ filename: 'error.log' })] });

D. const logger = winston.createLogger({ transports: [new winston.transports.File({ filename: 'error.log', level: 'info' }), new winston.transports.Console()] });

Solution

1. Step 1: Understand transport level filtering

   To log errors to file only, set level: 'error' on File transport.

2. Step 2: Ensure console logs all levels

   Console transport without level logs all messages by default.

3. Step 3: Check options

   const logger = winston.createLogger({ transports: [new winston.transports.Console(), new winston.transports.File({ filename: 'error.log', level: 'error' })] }); matches this setup: Console logs all, File logs errors only.

4. Final Answer:

   const logger = winston.createLogger({ transports: [new winston.transports.Console(), new winston.transports.File({ filename: 'error.log', level: 'error' })] }); -> Option A

5. Quick Check:

   File logs errors, console logs all = B [OK]

Hint: Set level on file transport only to filter errors [OK]

Common Mistakes:

• Setting wrong levels on transports
• Reversing console and file roles
• Omitting filename or level in file transport