Log services: Difference between revisions

Line 213:

* LogServerProxy object - sends log data via HTCS (see [[TMA_services]])

* ~~LogGetterLogger~~ object - retains log data which can be later retrieved by [[#lm:get]]:

* CustomSinkBuffer object - retains log data which can be later retrieved by [[#lm:get]]:

** When processes log via [[#lm]] service, some code analyzes the log packet, locates the TextLog ([[#LogDataChunkKey]]) chunk (if present) and saves it's contents in a global buffer (therefore, only the actual log message gets retained).

** Log packets are only analyzed/retained after enabling it (by calling [[#StartLogging]]), and the [[#GetLog]] command just reads data from the global buffer.

Line 222:

** When an [[#ILogger]] gets created, this object will send a packet containing the logger's process ID and a LogSessionBegin chunk, telling the remote connection that a new process has started logging. Analogously, when the logger gets destroyed, a simple packet with the process ID and a LogSessionEnd chunk gets sent, telling the remote connection that the process has stopped logging.

** As mentioned above, the flush thread will tell this object to send a simple packet with a LogPacketDropCount chunk after flushing succeeds (and if there any dropped packets).

** These event log packets are logged via the LogBuffer object, like process logs, but they are not analized by the ~~LogGetterLogger~~ object since they have no text to be saved.

** These event log packets are logged via the LogBuffer object, like process logs, but they are not analized by the CustomSinkBuffer object since they have no text to be saved.

* LogBuffer object - responsible for flushing log packets:

@@ Line 213: / Line 213: @@
 * LogServerProxy object - sends log data via HTCS (see [[TMA_services]])
-* LogGetterLogger object - retains log data which can be later retrieved by [[#lm:get]]:
+* CustomSinkBuffer object - retains log data which can be later retrieved by [[#lm:get]]:
 ** When processes log via [[#lm]] service, some code analyzes the log packet, locates the TextLog ([[#LogDataChunkKey]]) chunk (if present) and saves it's contents in a global buffer (therefore, only the actual log message gets retained).
 ** Log packets are only analyzed/retained after enabling it (by calling [[#StartLogging]]), and the [[#GetLog]] command just reads data from the global buffer.
@@ Line 222: / Line 222: @@
 ** When an [[#ILogger]] gets created, this object will send a packet containing the logger's process ID and a LogSessionBegin chunk, telling the remote connection that a new process has started logging. Analogously, when the logger gets destroyed, a simple packet with the process ID and a LogSessionEnd chunk gets sent, telling the remote connection that the process has stopped logging.
 ** As mentioned above, the flush thread will tell this object to send a simple packet with a LogPacketDropCount chunk after flushing succeeds (and if there any dropped packets).
-** These event log packets are logged via the LogBuffer object, like process logs, but they are not analized by the LogGetterLogger object since they have no text to be saved.
+** These event log packets are logged via the LogBuffer object, like process logs, but they are not analized by the CustomSinkBuffer object since they have no text to be saved.
 * LogBuffer object - responsible for flushing log packets: