robotframework-reportportal: Required LEVEL definition for report portal differ from robot

[doguz2509]

Not relevant for target tests and extra information printed into RF report, when executing with levels DEBUG/TRACE

Describe the solution you'd like Option to define report-portal debug level separately from robot

[HardNorth]

@doguz2509 Well, this issue is nothing to do with ReportPortal. Our agent uses standard Python logging framework to log its own debug information, and Robot Framework intercepts everything what was logged by its handler and puts it in report. The very same Robot Framework does not provide a way of filtering report output leaving just --loglevel parameter to control verbosity. So why should we bother?

Luckily to you there is a way to mute our listeners, I added it in our examples. You can do that by setting higher level of logging to each of our module in runtime: https://github.com/reportportal/examples-python/blob/master/robotframework/robot/library/Log.py#L36

And then call that method from a common initialization point, E.G.: https://github.com/reportportal/examples-python/blob/master/robotframework/robot/__init__.robot#L3

That's how my log looked before:

And after:

Those request logs are related to urllib3 library, a common library for any HTTP request. You may loose your REST API logs if I mute them also.

[doguz2509]

Thanks a lot Was helpfully 👍

16 июня 2022 г., в 21:15, Vadzim Hushchanskou @.***> написал(а):

 Closed #109 as completed.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.