D4Science Infrastructure

Luca Frosini wrote:

I think a template in needed.

It's a template already, you can find it in library/roles/smartgears/smartgears/templates/

The section using different files for access and accounting must disappears because causes a lower level logging in ghn.log.

I don't understand. Is it a bug on the logback configuration or in how it's used inside one of the libraries?
In the first case, feel free to propose a fix for the template. Otherwise we should better fix smartgears.

Moreover, the possibility to change the log level for a certain package shoul be supported as argument when running the playbook.

We can do it with variables (and so when running the playbook, too. But I prefer a written variable, so that we can know the log level from inspecting the playbook.
Right now only a global log level change is supported, but we can have a different variable for each logger, all set by default to the same value.

Andrea Dell'Amico wrote:

Luca Frosini wrote:

I think a template in needed.

It's a template already, you can find it in library/roles/smartgears/smartgears/templates/

Ok I found it

The section using different files for access and accounting must disappears because causes a lower level logging in ghn.log.

I don't understand. Is it a bug on the logback configuration or in how it's used inside one of the libraries?
In the first case, feel free to propose a fix for the template. Otherwise we should better fix smartgears.

I don't think the issue is on smartgears. I think the problem has to be search in the configuration.

Moreover, the possibility to change the log level for a certain package shoul be supported as argument when running the playbook.

We can do it with variables (and so when running the playbook, too. But I prefer a written variable, so that we can know the log level from inspecting the playbook.
Right now only a global log level change is supported, but we can have a different variable for each logger, all set by default to the same value.

Yes we should allow to set different log level(s) for different package(s). The package(s) and the log level can be specified in the playbook as you suggest. Infact we can also decide to set different level in the different playbook for dev and prod.

@luca.frosini@isti.cnr.it @lucio.lelii@isti.cnr.it can you come up with a refactored logback.xml template, starting from the one in the ansible repository?

@andrea.dellamico@isti.cnr.it I'll check it asap