Skip to content

use ewokscore task logs instead of pypushflow logs because less verbose

Wout De Nolf requested to merge reduc_ppf_log_level into main

The logs in /var/log/bes have the inData of every workflow task which looks like this

2024-11-02 15:52:30,388 INFO  [67263c3bca0241534da6e3dd] [MXPressA] [<InputMergeActor> Input merger of 'Retrieve flux from ISPyB'] triggered with inData =
 {'_noinput': {'execinfo': {'contexts': {'job': ['67263c3bca0241534da6e3dd'],
                                        'workflow': ['MXPressA']},
                           'engine': 'ppf',
... [280 lines]

This is too much and makes the logs unreadable. In addition, looking in besgui with the BES request id (which is also the ewoks job id) 67263c3bca0241534da6e3dd gives you the same information.

In this MR I'm setting the pypushflow log level to WARNING and instead ewokscore to INFO. So we keep the logging of the start and end of each workflow task but without printing the inData.

Edited by Wout De Nolf

Merge request reports