Recent log investigation showed that anything logged in response to client requests can be a problem because client requests are hundreds or thousands more frequent than the back end of the pricenode (interaction with providers). Logging outlier and blue rate transformations quickly fills the log, using up disk space and preventing analysis of other issues.
This PR implements a gating mechanism for selected logging. The result is logging of outlier and blue rate transformations is reduced to one per minute instead of hundreds per minute.
Recent log investigation showed that anything logged in response to client requests can be a problem because client requests are hundreds or thousands more frequent than the back end of the pricenode (interaction with providers). Logging outlier and blue rate transformations quickly fills the log, using up disk space and preventing analysis of other issues.
This PR implements a gating mechanism for selected logging. The result is logging of outlier and blue rate transformations is reduced to one per minute instead of hundreds per minute.