log4js-node / log4js-node/logstashUDP

Shutdown does not wait for in-flight log messages

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
19
Forks
4
PR merge metrics
No merged PRs in 30d

Description

See https://github.com/log4js-node/log4js-node/issues/520 for details.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the linked log4js-node issue #520 first; no repository file or test is named here. Then locate the logstashUDP appender’s shutdown entry point and determine how in-flight log messages are tracked. Done means shutdown waits for those messages, with behavior covered by a regression test if the repository has a test entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.