You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: logger/README.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
## Logger service:
1
+
## Logger Service:
2
2
3
-
The Logger Service operates as a standalone component/service within the Jugalbandi (JB) Manager system. Its primary purpose is to record and manage metrics from other key services: api, language, channel, flow and retriever. These metrics provide valuable insights into the performance of each service, facilitate debugging, and help track user requests and responses as well as the time taken by each service to process them.
3
+
The logger service operates as a standalone component/service within the Jugalbandi (JB) Manager system. Its primary purpose is to record and manage metrics from other key services: api, language, channel, flow and retriever. These metrics provide valuable insights into the performance of each service, facilitate debugging, and help track user requests and responses as well as the time taken by each service to process them.
4
4
5
5
### Core Functionality
6
6
@@ -10,14 +10,14 @@ The Logger Service operates as a standalone component/service within the Jugalba
10
10
11
11
### Workflow
12
12
13
-
When a request or a response passes through a service (api, channel, language, flow, or retriever), a logger object,containing service-specific details, is created. These details include relevant identifiers (e.g., User ID, Turn ID, Channel ID) and metadata specific to the service (e.g., Message Type, Intent, Translation Type).
14
-
This logger object is sent asynchronously to the Logger Service via a Kafka queue. The Logger service receives the logger object from its kafka queue and processes the message by:
13
+
When a request or a response passes through a service (api, channel, language, flow, or retriever), a logger objectcontaining service-specific details, is created. These details include relevant identifiers (e.g., User ID, Turn ID, Channel ID) and metadata specific to the service (e.g., Message Type, Intent, Translation Type).
14
+
This logger object is sent asynchronously to the logger service via a kafka queue. The logger service receives the logger object from its kafka queue and processes the message by:
15
15
16
-
1.**Unpacking and Identifying the Source Service:**
16
+
1.**Unpacking and identifying the source service:**
17
17
- The message is unpacked upon receipt.
18
18
- The source service from which the message originated is identified.
19
19
20
-
2.**Logging the Details into the Respective Table:**
20
+
2.**Logging the details into the respective table:**
21
21
- The corresponding service’s logging function is called in the CRUD layer.
22
22
- This function in the CRUD layer performs the following actions:
0 commit comments