
Security News
Deno 2.6 + Socket: Supply Chain Defense In Your CLI
Deno 2.6 introduces deno audit with a new --socket flag that plugs directly into Socket to bring supply chain security checks into the Deno CLI.
binder-logging
Advanced tools
Consistent logging reader/writer functions for all Node-based Binder modules
Takes a configuration file (the default version in conf/example.main) that specifies how to
The example configuration file included in the module has these defaults:
{
"host": "localhost",
"testing": true,
"logstash": {
"port": 8050,
"configDir": "~/binder-control/services/logging/logstash/"
},
"elasticsearch": {
"port": 8052,
"dir": "/data/binder/elasticsearch"
},
"kibana": {
"port": 8053
},
"streaming": {
"port": 2121
}
}
binder-control can launch Docker containers for Elasticsearch, Logstash and Kibana (with the same default values) through the binder-control start-service logging command. If you'd prefer to use existing logging infrastructure, specify the custom host/port in the config file.
If testing is enabled, the Winston logger will output to both Logstash and stdout (only Logstash otherwise).
npm install binder-logging
lib/reader.js contains functions that wrap Elasticsearch queries to make it simpler to search through Binder logs. If you'd prefer to monitor a realtime stream of build logs, the streamLogs function is available (which will connect to Logstash's WebSocket output).
BinderLogReader.getLogs(opts, cb)Get all historical logs, optionally matching an app name and optionally between before/after times
app string - app name to filter onbefore string - ISO8601 GMT timestampafter string - ISO8601 GMT timestampcb function - callback(err, msgs)BinderLogReader.streamLogs(opts)Stream logs for a given app (mandatory option), optionally since an after timestamp. Returns a through stream
app string - app name to filter onafter string - ISO8601 GMT timestampvar getReader = require('binder-logging/lib/reader')
var reader = getReader({ host: '<custom logging host>' })
lib/writer.js exposes a getInstance function that will return a Winston logger given a logger name. This logger exposes the standard logging api (logger.info, logger.error, ...).
getInstance(name)Returns a Winston logger that's connected to the Binder logging stack
name string - logger name (one logger will be created per name, per process)var getLogger = require('binder-logging/lib/writer')
var logger = getLogger('<logger name>')
logger.info('this is an info message')
FAQs
Module for consistent logging across Binder components
The npm package binder-logging receives a total of 0 weekly downloads. As such, binder-logging popularity was classified as not popular.
We found that binder-logging demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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.

Security News
Deno 2.6 introduces deno audit with a new --socket flag that plugs directly into Socket to bring supply chain security checks into the Deno CLI.

Security News
New DoS and source code exposure bugs in React Server Components and Next.js: what’s affected and how to update safely.

Security News
Socket CEO Feross Aboukhadijeh joins Software Engineering Daily to discuss modern software supply chain attacks and rising AI-driven security risks.