-
Notifications
You must be signed in to change notification settings - Fork 12
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
Logs: Add parameter for minimum severity #329
Comments
Do you mean filtering when retrieving the logs? This would imply that the backend always has to keep track of all log levels, which might not be desirable for large jobs (debug level might be very verbose). Alternative (or additional) approach: user has to specify minimum log level (e.g |
Yes, I was speaking about the retrieval. If the back-end doesn't provide some levels, that is fine. The contract doesn't enforce any level. Allowing the user to select what he wants to log when submitting the process is also a good idea. |
The idea of a job/service/...-specific flag for log-levels came up again in an internal discussion where @clausmichele proposed:
|
It could be useful to filter logs returned to a client by a minimum severity. So for example, if I pass
severity=warning
to the back-end, it should only return warnings and errors, but not info or debug messages.The text was updated successfully, but these errors were encountered: