New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloud handler always sets level to DEBUG #2256
Comments
Thanks for opening the issue @kchaliki! I think we should update that line to respect the level set by |
@kchaliki talking about this more with the core team this is not as trivial to implement for all distributed agents to honor from config; is there a specific use case that filtering the debug logs from the UI in cloud isn't good enough for? |
Hi @lauralorenz I am sure we can get by with the UI filter. I just thought streaming debug logs, particularly from all sorts of libraries people use, might put unnecessary stress on the system, obviously having to click around every time to filter is also a minor nuisance but definitely not a priority. |
Hi @lauralorenz - a good example of a use-case where it would be nice to have this is when trying to debug something where it's sensible to locally log potentially sensitive information that shouldn't be leaked through the logs when running through Cloud. |
@arlobryer - in that case it would be safer to use |
Thanks @arlobryer for the use case; RT on the |
The default of DEBUG is no longer the case, closing |
Description
A clear description of the bug
It looks like when logging to cloud, the log level config is ignored and the level is fixed to debug in the code (prefect/utilities/logging.py:208). Not that upon construction of the hander it actually reads the config but the harcoding is done straight after.
Expected Behavior
What did you expect to happen instead?
The log level config to be respected.
Reproduction
A minimal example that exhibits the behavior.
Environment
Any additional information about your environment
Optionally run
prefect diagnostics
from the command line and paste the information hereThe text was updated successfully, but these errors were encountered: