Gathering detailed insights and metrics for @log4js-node/logstash-http
Gathering detailed insights and metrics for @log4js-node/logstash-http
Gathering detailed insights and metrics for @log4js-node/logstash-http
Gathering detailed insights and metrics for @log4js-node/logstash-http
npm install @log4js-node/logstash-http
73.4
Supply Chain
75.2
Quality
77.6
Maintenance
50
Vulnerability
100
License
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
13 Stars
94 Commits
8 Forks
5 Watching
5 Branches
3 Contributors
Updated on 15 Aug 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
9.1%
371
Compared to previous day
Last week
11.8%
2,865
Compared to previous week
Last month
4.9%
10,727
Compared to previous month
Last year
31.9%
134,999
Compared to previous year
The logstash appenders for log4js send NDJSON formatted log events to logstash receivers. This appender uses HTTP to send the events (there is another logstash appender that uses UDP).
1npm install log4js @log4js-node/logstash-http
type
- @log4js-node/logstash-http
url
- string
- logFaces receiver servlet URLapplication
- string
(optional) - used to identify your application's logslogChannel
- string
(optional) - also used to identify your application's logs [but in a more specific way]logType
- string
(optional) - used for the type
field in the logstash datatimeout
- integer
(optional, defaults to 5000ms) - the timeout for the HTTP request.agent
- http.Agent | https.Agent
(optional) - used to configure the requests being sent out if needed.This appender will also pick up Logger context values from the events, and add them as p_
values in the logFaces event. See the example below for more details.
1log4js.configure({ 2 appenders: { 3 logstash: { 4 type: "@log4js-node/logstash-http", 5 url: "http://localhost:9200/_bulk", 6 application: "logstash-log4js", 7 logType: "application", 8 logChannel: "node", 9 }, 10 }, 11 categories: { 12 default: { appenders: ["logstash"], level: "info" }, 13 }, 14}); 15 16const logger = log4js.getLogger(); 17logger.addContext("requestId", "123"); 18logger.info("some interesting log message"); 19logger.error("something has gone wrong");
This example will result in two log events being sent to your localhost:9200
. Both events will have a context.requestId
property with a value of 123
.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
Found 0/1 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
11 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More