There are a lot of log messages that have no additional information:
task-result changed
node changed
node unchanged
Which are useful, but when you are running in production with potentially hundreds of workflows running at the same time these flood the INFO logs with useless information. It would be useful to put these as debug logs, so we can still access them if needed, but so that we can turn them off in production more easily!
Use Cases
Pretty much everywhere. At the moment we just filter these logs out via log indexing, but that is annoying to maintain!
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
Summary
There are a lot of log messages that have no additional information:
Which are useful, but when you are running in production with potentially hundreds of workflows running at the same time these flood the INFO logs with useless information. It would be useful to put these as debug logs, so we can still access them if needed, but so that we can turn them off in production more easily!
Use Cases
Pretty much everywhere. At the moment we just filter these logs out via log indexing, but that is annoying to maintain!
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.