cf-nodejs-logging-support - npm Package Compare versions

Comparing version 3.0.2 to 3.0.3

cf-nodejs-logging-support-core/log-core.js

		@@ -457,3 +457,3 @@ var util = require('util');
		var payload = verifyAndDecodeJWT(token, dynLogLevelKey);
		console.log(payload);

		if(payload == null) {
		@@ -460,0 +460,0 @@ return null;

package.json

		{
		"name": "cf-nodejs-logging-support",
		"version": "3.0.2",
		"version": "3.0.3",
		"description": "Logging tool for Cloud Foundry",
		@@ -5,0 +5,0 @@ "keywords": [

README.md

		@@ -121,3 +121,3 @@ # Node.js Logging Support for Cloud Foundry

		With custom fields added to custom_fields field. Keep in mind, that the last argument is handled as custom_fields object, if it is an object.
		With custom fields added to custom_fields field. Keep in mind that the last argument is handled as custom_fields object, if it is an object.
		```js
		@@ -171,3 +171,3 @@ logMessage("info", "Test data %j", {"field" :"value"});

		This library supports six logging levels: error, warn, info, verbose, debug and silly. Make sure, that your JWT specifies one of them in order to work correctly. It is also important to make sure, that the JWT has not been expired, when using it.
		This library supports six logging levels: error, warn, info, verbose, debug and silly. Make sure that your JWT specifies one of them in order to work correctly. It is also important to make sure that the JWT has not been expired, when using it.

		@@ -240,3 +240,3 @@ ##### 2 Providing the public key
		### Fixed Values for Network Logging (will impact log parsing if used incorrectly)
		Possibility to tailor logs to your needs, you can for example change the msg field for Network-logs to a find them in Human readable format:
		Possibility to tailor logs to your needs, you can for example change the msg field for Network-logs to find them in the Human readable format:
		```js
		@@ -243,0 +243,0 @@ log.overrideNetworkField("msg", YOUR_CUSTOM_MSG);

New alerts