log4js-node/log4js-node

Expose worker id as a layout pattern specifier

Open

#740 opened on Jun 26, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (5,721 stars) (787 forks)batch import
good first issuehelp wanted

Description

While the pid is available (via %z) it would be good to also make the worker id available when the cluster module is in use. I guess it should evaluate to 0 if the process is not a worker

Contributor guide

Tech stack
javascriptnodejs
Domain
backenddeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of log4js layout patternsFamiliarity with Node.js cluster module
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the layout pattern implementation in log4js, likely in lib/layouts.js. Look at how '%z' (pid) is resolved to understand the pattern. The worker id can be obtained via cluster.worker.id when cluster.isWorker. If not a worker, default to 0. Add support for a new token, e.g., '%w'. Test with a cluster setup to verify output.