-
Notifications
You must be signed in to change notification settings - Fork 176
DIRAC v6r19
[In preparation]
The v6r19 release introduces a new OPTIONAL feature: the pilots logging service. The pilots logging service is very well documented in the official DIRAC documentation, so please refer to that. Operationally, if you want to enable it, you will need an MQ system like RabbitMQ, and to do the following steps:
The new DB PilotsLoggingDB should be defined, then the tables in the databases should be created by the PilotsLogging service
new PilotsLogging service (via sysadmin-cli):
install service WorkloadManagement PilotsLogging
The PilotRequirements table from PilotAgentsDB can be removed:
USE PilotAgentsDB;
DROP TABLE IF EXISTS PilotRequirements;
The logging tool gLogger is now based on the standard logging Python library and includes some changes that you can consult in the official DIRAC documentation. The major changes that you have to take care of first are the following:
Before, you had to define your Backends in the LogBackends option and to specify their parameters in the BackendsOptions section. Now, the Backends configuration becomes more readable thanks to a new section named BackendsConfig, and the previous one has to be removed, even if it is still compatible with the new logging tool.
Thus, your current Backends configuration...
LogBackends = <backend1>, <backend2>, <backend3>
BackendOptions
{
<param backend2> = <value1>
<param backend3> = <value2>
}
... should become:
LogBackends = <backend1>, <backend2>, <backend3>
BackendsConfig
{
<backend2>
{
<param backend2> = <value1>
}
<backend3>
{
<param backend3> = <value2>
}
}
Note that the ProtocolName option in the configuration is not supported anymore. It is now replaced by the PluginName option.