Possibility of ignoring certain logs by setting a log level

[mhashas]

Hi,

First of all, thank you for the library, super useful. Would it be possible to be able to set the log level so that we can ignore certain logs? For example, I don't want to get the logs that 0 tasks were found, but I do want to get the log that x tasks were found. Right now I subclassed the task executor and others to implement it myself, but it s a bit dirty

[mstuebner]

@mhashas We currently also sort out the best way to log relevant information and avoid to fill our OpenSearch instance with senseless information. Am I right that the "= tasks were found" is only ONE example of many? How did you classify logs to relevant/non-relevant?

Can you add a link to your implementation here?

[bachi76]

Same issue here. I suggest you set the log level to DEBUG for those, so a long polling will not issue any log events of INFO at all.

Here's what I get on each and every poll, from each worker:

2022-06-28 00:49:46,277 [INFO] [WORKER_ID:2] 0 External task(s) found for Topics: step3, Process variables: None

2022-06-28 00:49:46,277 [INFO] [WORKER_ID:2][TOPIC:step3] no External Task found for Topics: step3, Process variables: None

2022-06-28 00:49:46,278 [INFO] [WORKER_ID:2] Fetching and Executing external tasks for Topics: step3 with Process variables: None

2022-06-28 00:49:46,278 [INFO] [WORKER_ID:2] Fetching and Locking external tasks for Topics: step3 with Process variables: None

All of them are essentially debug level messages, not info.

Note that I have set "isDebug": False

[royalzzz]

This issue is particularly prominent when subscribing to multiple tasks. I hope the team in this repository can pay attention to the impact of this issue.