-
Notifications
You must be signed in to change notification settings - Fork 26
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
workflow-handler-proxy log level #105
Comments
hey @jabstone I think you're right - there shouldn't be any need for this to be logging at Cheers! |
Just submitted a PR. Appreciate the quick reply and help on this issue. |
Thanks @jabstone - your changes are in @node-ts/bus-workflow 0.6.6 |
Thank you so much for the quick turnaround. Appreciate it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello. We're using the postgres persistence transport and it's working awesome. The one thing I wish I could change is the log level when saving a workflow. In the postgres saveWorkFlowData method the log level is set to debug and works fine. However, the workflow-handler-proxy that calls it appears to write logs at the info level. Actually, the real issue is the logger.info in the proxy includes the entire payload. We're persisting a lot of data between workflow handlers and this logger.info call is destroying our log files. :) Is this by design or an oversight? Ideally, the logger.info would log the workflow name and id and the logger.debug would log the payload. Is this something you would consider changing? I'm happy to submit a PR if necessary. Thanks for this awesome project. It works great.
The text was updated successfully, but these errors were encountered: