@mimik/sumologic-winston-logger 2.2.1 → 2.2.2

package/README.md

@@ -160,7 +160,7 @@ To learn more about setting this environment variable, see the section, _Finding
 
 #### Finding SumoLogic endpoint and collector code ####
 
-To find the values that you will apply the environment variables, `SUMO_LOGIC_ENDPOINT` and `SUMO_LOGIC_COLLECTOR_CODE`, in the SumoLogic Control Panel, goto: Manage > Collection, and get the source category
+To find the values that you will apply the environment variables, `SUMO_LOGIC_ENDPOINT` and `SUMO_LOGIC_COLLECTOR_CODE`, in the SumoLogic Control Panel, go to: Manage > Collection, and get the source category.
 
 ![Screen Shot 2016-10-10 at 2.03.31 PM.png](https://bitbucket.org/repo/xbXGRo/images/3258406172-Screen%20Shot%202016-10-10%20at%202.03.31%20PM.png)
 
@@ -194,11 +194,11 @@ Formatting console logs is left to winston, except that some stackTrace info is
 
 Formatting of SumoLogic logs is handled by this module in the following ways:
 
-* only the first argument is used as the message
-* one metadata object can be passed as a parameter; its properties are included in the log entry
-* structured stackTrace info is added to every log except when NO_STACK is set to 'yes'
-* if the last parameter is a string it will be considered as a `correlationId`
-* if the last parameter is a plain object **and** there is already an earlier metadata object, its properties are merged into the log entry at the top level (alongside `serverType`/`serverId`) — this is the _extra fields_ feature
+* only the first argument is used as the message,
+* one metadata object can be passed as a parameter; its properties are included in the log entry,
+* structured stackTrace info is added to every log except when NO_STACK is set to 'yes',
+* if the last parameter is a string it will be considered as a `correlationId`,
+* if the last parameter is a plain object **and** there is already an earlier metadata object, its properties are merged into the log entry at the top level (alongside `serverType`/`serverId`) — this is the _extra fields_ feature.
 
 
 ### Logging Examples ###
@@ -232,7 +232,7 @@ The log() method is also supported, and adds a level parameter in position 1.
 
 Tailing allows you to scroll through log output in real time. You can trail log data in SumoLogic.
 
-To trail in SumoLogic go to Search > Live Tail in the SumoLogic user interface and enter `sourceCategory=<source category>` in the search bar, where `<source category>` is the log you want to trail. Then click, Run
+To trail in SumoLogic go to Search > Live Tail in the SumoLogic user interface and enter `sourceCategory=<source category>` in the search bar, where `<source category>` is the log you want to trail. Then click, Run.
 
 |Example|
 |---|

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mimik/sumologic-winston-logger",
-  "version": "2.2.1",
+  "version": "2.2.2",
   "description": "Log wrapper for sumo, s3, kinesis and winston",
   "main": "./index.js",
   "type": "module",
@@ -32,9 +32,9 @@
   },
   "dependencies": {
     "@mimik/lib-filters": "^2.0.8",
-    "@aws-sdk/client-s3": "3.1007.0",
-    "@aws-sdk/client-kinesis": "3.1007.0",
-    "@smithy/node-http-handler": "4.4.14",
+    "@aws-sdk/client-s3": "3.1008.0",
+    "@aws-sdk/client-kinesis": "3.1008.0",
+    "@smithy/node-http-handler": "4.4.16",
     "axios": "1.13.6",
     "winston": "3.19.0",
     "winston-transport": "4.9.0"