Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
@hmcts/nodejs-logging
Advanced tools
[![Greenkeeper badge](https://badges.greenkeeper.io/hmcts/nodejs-logging.svg)](https://greenkeeper.io/)
A logging component used by Reform's Node.js applications. Some background info:
ALL
, TRACE
, DEBUG
, INFO
, WARN
, ERROR
, FATAL
and OFF
.LOG_LEVEL
, the default is INFO
.LOG_OUTPUT
, the default is human
:
human
- single line of a human readable outputsingle
- a single line of JSON outputmulti
- a multiline formatted JSON outputAdd it as your project's dependency:
yarn add @hmcts/nodejs-logging
Require it:
const { Logger } = require('@hmcts/nodejs-logging')
Set the logging configuration. Should be done once at application startup:
Logger.config({
microservice: 'your-service-name',
team: 'your-team',
environment: 'some-environemnt'
})
Then you can create a logger instance and use it to log information:
const logger = Logger.getLogger('app.js') // app.js is just an example, can be anything that's meaningful to you
logger.info({
message: 'Yay, logging!'
})
Optionally you can use the built-in Express access logger:
const { Express } = require('@hmcts/nodejs-logging')
app.use(Express.accessLogger())
It will log all requests made against your application. For example, a typical HTTP 404 log error when encountering an error would look like the following:
{
responseCode: 404,
message: 'Not Found',
fields: [],
level: 'ERROR',
environment: 'some-environemnt',
hostname: 'My-MacBook-Pro.local',
rootRequestId: '',
requestId: '',
originRequestId: '',
type: 'nodejs',
microservice: 'your-service-name',
team: 'your-team',
timestamp: '2017-01-27T11:27:23+00:00'
}
An Express middleware is provided which automatically populates request headers with request tracing IDs. Sample usage:
const { RequestTracing } = require('@hmcts/nodejs-logging')
app.use(RequestTracing.middleware)
Assuming your Express application servers as the system's entry point which serves user UI, this middleware will intercept user requests and set Root-Request-Id
and Request-Id
headers on it. If the incoming request comes from a different service which already populated those values, they will be forwarded.
Apart from populating the headers, access to request tracing information is available at any point during request processing, e.g.:
const id = RequestTracing.getCurrentRequestId()
We can also access the original request:
const request = RequestTracing.retrieveInitialRequest()
These features are enabled by continuation-local-storage module.
Just do
yarn test
This project is licensed under the MIT License - see the LICENSE file for details.
FAQs
[![Greenkeeper badge](https://badges.greenkeeper.io/hmcts/nodejs-logging.svg)](https://greenkeeper.io/)
The npm package @hmcts/nodejs-logging receives a total of 0 weekly downloads. As such, @hmcts/nodejs-logging popularity was classified as not popular.
We found that @hmcts/nodejs-logging demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 16 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.