From fd0b153700615954ec0147d5e15194b5cdbb6e45 Mon Sep 17 00:00:00 2001 From: Bertrand Rigaud Date: Tue, 26 Sep 2023 14:25:01 +0200 Subject: [PATCH] add comments --- .../ServerInstallations/tornadoComponentLogs.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/AdministratorGuide/ServerInstallations/tornadoComponentLogs.rst b/docs/source/AdministratorGuide/ServerInstallations/tornadoComponentLogs.rst index d748e63834e..300383a28bf 100644 --- a/docs/source/AdministratorGuide/ServerInstallations/tornadoComponentLogs.rst +++ b/docs/source/AdministratorGuide/ServerInstallations/tornadoComponentLogs.rst @@ -157,7 +157,7 @@ dirac-json.conf (Add all needed components and choose the output you want):: ``dirac-json.conf`` is the main file, it defines different steps such as:: [SERVICE] where we describe our json parser (from dirac Json log backend) [INPUT] where we describe dirac components log file and the way it will be parsed (json) - [FILTER] where we apply modifications to parsed data, for example adding a levelname "DEV" whenever logs are not well formatted, typically "print" in code, or adding fields like hostname to know from wich host logs are coming, but also more complex treatments like in dirac.lua script (described later) + [FILTER] where we apply modifications to parsed data, for example adding a levelname "DEV" whenever logs are not well formatted, typically "print" in code, or adding fields like hostname to know from which host logs are coming, but also more complex treatments like in dirac.lua script (described later) [OUTPUT] where we describe formatted logs destination, here, we have stdout, files on disks and elasticsearch. dirac-parsers.conf::