From d229e5a63fe44a0e8cf70de6bdd3fe79798829f7 Mon Sep 17 00:00:00 2001
From: Nabraj Khatri <101577964+nabrajkhatri@users.noreply.github.com>
Date: Thu, 20 Oct 2022 11:41:35 -0500
Subject: [PATCH] Added additional fields and externalized the parameters

each api/developer has its own custom field added. this makes log indexing and parsing very tedious and not maintainable.
based on inputs from various customers and MuleSoft practice experts, additional fields are added.
These additional fields are pre-populated and externalized.
---
 README.md | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/README.md b/README.md
index f18c5e0..b646318 100644
--- a/README.md
+++ b/README.md
@@ -49,6 +49,37 @@ PS2. For EU Control Plane deployment you have to modify the `<distributionManage
 
 ##  Release notes [HERE](https://github.com/mulesoft-consulting/json-logger/blob/mule-4.x/json-logger/README.md)
 
+## Dependencies
+with latest changes to add additional fields and making them externalized, you need to add Global element properties file, for example :
+properties/json-logger.yaml (sample values are provided below)
+
+### JSON Logger configuration
+ 
+#### Indicate which fields should not be logged (it can take values content and message and needs to be comma separated)
+#### Specifies data to be masked in log output. Populate as necessary. Example: $..firstName,$..lastName
+
+json-logger:
+    disabled-fields: ""
+    data-to-mask: ""
+    orgName : SFCC
+    application:
+      version : 1.1.11
+      name : SALESFORCE_SYS_API
+    cloudhub:
+      environment : DEV1
+    entity: JOB_ORDER
+    entityId: JO_ID_18990
+    businessEvent: JO FILLED
+    sourceSystem: SALESFORCE
+    targetSystem: WORKDAY
+    retryCounter: "0"
+    errorSeverity: MAJOR
+    processName: RAW_QUEUE_VALIDATION
+    errorType: ErrorType_Dynamic
+    errorMessage: ErrorMessage_Dynamic
+    clientId: clientId_process_api_980
+    category: com.json-logger.SALESFORCE_SYS_API.RAW_QUEUE_VALIDATION
+
 ## Author
 
 * **Andres Ramirez** [Slack: @andres.ramirez / Email: andres.ramirez@mulesoft.com]