logzio-nodejs
Advanced tools
Comparing version 2.0.3-beta to 2.0.3
@@ -46,3 +46,2 @@ const request = require('request-promise'); | ||
debug = false, | ||
verbose = false, | ||
numberOfRetries = 3, | ||
@@ -70,3 +69,2 @@ supressErrors = false, | ||
this.debug = debug; | ||
this.verbose = verbose; | ||
this.numberOfRetries = numberOfRetries; | ||
@@ -250,9 +248,3 @@ this.supressErrors = supressErrors; | ||
} | ||
_verbose(msg) { | ||
if (this.verbose) this.internalLogger.log(`logzio-nodejs verbose: ${msg}`); | ||
} | ||
_tryAgainIn(sleepTimeMs, bulk) { | ||
@@ -297,7 +289,2 @@ this._debug(`Bulk #${bulk.id} - Trying again in ${sleepTimeMs}[ms], attempt no. ${bulk.attemptNumber}`); | ||
this._debug(`Sending bulk of ${bulk.msgs.length} logs`) | ||
let idx = 1; | ||
bulk.msgs.forEach(msg => { | ||
this._verbose(`Log #${idx} sturcture: ${JSON.stringify(msg)}`) | ||
idx ++; | ||
}); | ||
return request.post(options) | ||
@@ -304,0 +291,0 @@ .then(() => { |
{ | ||
"name": "logzio-nodejs", | ||
"description": "A nodejs implementation for sending logs to Logz.IO cloud service Copy of logzio-nodejs", | ||
"version": "2.0.3-beta", | ||
"version": "2.0.3", | ||
"author": "Gilly Barr <gilly@logz.io>", | ||
@@ -6,0 +6,0 @@ "contributors": [ |
@@ -45,3 +45,2 @@ ![Build Status](https://travis-ci.org/logzio/logzio-nodejs.svg?branch=master) | ||
* **debug** - Should the logger print debug messages to the console? Default: `false` | ||
* **verbose** - Should the logger print verbose 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. | ||
@@ -48,0 +47,0 @@ * **timeout** - The read/write/connection timeout in milliseconds. |
@@ -18,3 +18,2 @@ const sinon = require('sinon'); | ||
myOptions.debug = true; | ||
myOptions.verbose = true; | ||
myOptions.host = dummyHost; | ||
@@ -21,0 +20,0 @@ myOptions.sendIntervalMs = options.sendIntervalMs || 1000; |
Deprecated
MaintenanceThe maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
0
0
1
52524
878
146