To help you get started, we've collected the most common ways that logzio-nodejs is being used within popular public projects.

DFEAGILEDEVOPS / MTC / checkapi / index.js View on Github

const http = require('http')
const fs = require('fs')
const path = require('path')
var os = require('os')
const machineName = os.hostname()
const processId = process.pid

const azure = require('azure-storage')
const storageService = azure.createTableService()
const storageTargetName = 'completechecks'
const entityGenerator = azure.TableUtilities.entityGenerator
const uuid = require('uuidv4')
const debug = process.env.NODE_ENV !== 'production'
let logger
if (process.env.LOGZ_KEY) {
  logger = require('logzio-nodejs').createLogger({
    token: process.env.LOGZ_KEY,
    host: 'listener.logz.io',
    type: 'wac-spike-mtc'
  })
}

const log = (data) => {
  if (logger) {
    logger.log(data)
  }
}

// grab disk data...
let buildId
try {
  buildId = fs.readFileSync(path.join(__dirname, 'build.txt'))

View more ways to use logzio-nodejs

logzio-nodejs

NodeJS logger for Logz.io. The logger stashes the log messages you send into an array which is sent as a bulk once it reaches its size limit (100 messages) or time limit (10 sec) in an async fashion. It contains a simple retry mechanism which upon connection reset (server side) or client timeout, wait a bit (default interval of 2 seconds), and try this bulk again. It does not block other messages from being accumulated and sent (async). The interval increases by a factor of 2 between each retry until it reaches the maximum allowed attempts (3).

By default, any error is logged to the console. This can be changed by supplying a callback function.

Before you begin you will need:

• Nodejs with version 14.x or above

Sample usage

var logger = require('logzio-nodejs').createLogger({
    token: '__YOUR_ACCOUNT_TOKEN__',
    type: 'YourLogType'     // OPTIONAL (If none is set, it will be 'nodejs')
});


// sending text
logger.log('This is a log message');

// sending an object
var obj = {
    message: 'Some log message',
    param1: 'val1',
    param2: 'val2'
};
logger.log(obj);

Note: If logzio-js is used as part of a serverless service (AWS Lambda, Azure Functions, Google Cloud Functions, etc.), add logger.sendAndClose() at the end of the run. For example sync Lambda and async Lambda

Options

• token Mandatory. Your account token. Look it up in the Device Config tab in Logz.io
• type - Log type. Help classify logs into different classifications
• protocol - http, https or udp. Default: http
• host - Destination host name. Default: listener.logz.io
• port - Destination port. Default port depends on protocol. For udp default port is 5050, for http is 8070 and 8071 is for https
• sendIntervalMs - Time in milliseconds to wait between retry attempts. Default: 2000 (2 sec)
• bufferSize - The maximum number of messages the logger will accumulate before sending them all as a bulk. Default: 100.
• numberOfRetries - The maximum number of retry attempts. Default: 3
• debug - Should the logger print debug messages to the console? Default: false
• callback - A callback function called when an unrecoverable error has occured in the logger. The function API is: function(err) - err being the Error object.
• timeout - The read/write/connection timeout in milliseconds.
• addTimestampWithNanoSecs - Add a timestamp with nano seconds granularity. This is needed when many logs are sent in the same millisecond, so you can properly order the logs in kibana. The added timestamp field will be @timestamp_nano Default: false
• compress - If true the the logs are compressed in gzip format. Default: false
• internalLogger - set internal logger that supports the function log. Default: console.
• setUserAgent - Set false to send logs without user-agent field in request header. Default:true.
• extraFields - Adds your own custom fields to each log. Add in JSON Format, for example: extraFields : { field_1: "val_1", field_2: "val_2" , ... }.

Using UDP

A few notes are worth mentioning regarding the use of the UDP protocol:

• UDP has some limitations, and therefore it is not the recommended protocol:
  • There is no guarantee that the logs have been received.
  • UDP can't take advantage of the bulk API, so performance is sub-optimal.
• When using UDP, each message is sent separately, and not using the bulk API. This means that the meaning of bufferSize is slightly different in this case. The messages will still be sent separately, but the logger will wait for the buffer to reach the size specified before sending out all the messages. If you want each message to be sent out immediately, then set bufferSize = 1.

Update log

2.1.7

• upgrade axios to v1.6.4 (contributed by @gcagle3)

2.1.6

• Test node versions 14-20
• upgrade axios to v1.6.0 (contributed by @gcagle3)

2.1.5

• Add sourceIP as a new field to each log

2.1.4

• Replace from request to axios

2.0.4

• Add parameter to manage User-agent

2.0.3

• Add verbose logging to use in Azure serverless function

2.0.2

• Updated required fields for typescript

2.0.1

• Fixed sorting by nanosec-timestamp
• Added option to log string with an object
• Updated Typescript declaration for optional dependencies

2.0.0

• Added support for TypeScript
• End of support for node 6
• Upgrade dependencies due to security vulnerabilities

Scripts

• run npm install to install required dependencies
• run npm test to run unit tests