oneway6026
oneway60263w ago

logging

If I follow the user guide on how to add logging into a code: https://docs.buildship.com/logging and perform test on one specific node. Logs are not written into the logging panel. I have tried several times and it seems that is not written at all. It seems that only works with the test of the entire scenario. How can I perform troubleshooting of the issues in the node ?
Logging – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
Solution:
Hi @oneway6026 sent you an email, regarding this, you can followup on the email. The logging statements are working fine and showing up in your workflow. More info shared over email.
Jump to solution
21 Replies
Gaurav Chadha
Gaurav Chadha3w ago
Hi @oneway6026 currently logging only works on entire workflow testing, we'll add this to enable this feature for individual node test in future. Given this, the logging.log() should work with the mentioned steps. The logging statements you add in the node log should appear in the cloud log window on a full workflow test,
No description
oneway6026
oneway60263w ago
thank you for your quick answer Gaurav. I was expecting that as well, however, it is not the case.
Gaurav Chadha
Gaurav Chadha3w ago
It might be the issue on how you added logging statements, can you share your node logic where you have added logging statements along with screenshot of the log window after running testes?
oneway6026
oneway60263w ago
first thing that comes to my mind is that there is some kind of delay between build and production enviorment sure, give me a moment
oneway6026
oneway60263w ago
No description
oneway6026
oneway60263w ago
No description
oneway6026
oneway60263w ago
as you can see, I've tested this code on my server to confirm that is working inability to perform troubleshooting on a specific node is a big impediment as far as I'm concerned
Gaurav Chadha
Gaurav Chadha3w ago
from the screenshot it shows running state, can you close and refresh the logs and see, it should show completed and show you the logging.log statements.
oneway6026
oneway60263w ago
it is still the same, there is no log info
No description
oneway6026
oneway60263w ago
not even error log
Gaurav Chadha
Gaurav Chadha3w ago
can you submit via in-app we can check on your project?
oneway6026
oneway60263w ago
in-app?
Gaurav Chadha
Gaurav Chadha3w ago
Support Messages – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
oneway6026
oneway60263w ago
you mean support yes, sure
Solution
Gaurav Chadha
Gaurav Chadha3w ago
Hi @oneway6026 sent you an email, regarding this, you can followup on the email. The logging statements are working fine and showing up in your workflow. More info shared over email.
oneway6026
oneway60263w ago
Hello Gaurav, thank you for the info. It seems that you didn't understand me well. Let me try to explain it. When I said , logging is not working, I was trying to point to the fact that when you ad logging.log("TEST"); and hit save, that log is not visible even when you perform testing of the entire flow. it seems that there is some kind of a delay between save enviorment and operational enviroment logs are visible sometimes several hours lates, sometimes several days later So, it seems that problem is not logging part but operational architecture
Gaurav Chadha
Gaurav Chadha3w ago
You can click Refresh after execution is completed, the logs should show up after ~1 minute. Sent you the working logging screenshot of your worklow over email.
No description
oneway6026
oneway60263w ago
that part works fine. logs are visible after execution I am not refering to that but, execution is not using the code that I saved, but some earlier version if you perform: 1. Change of the code 2. Save the code 3. Repeat step 1 and 2 several times 4. Test entire solution Result: it is executed some version of the code, but not the last one I have sent you the video , it is visible there it is probably some sync issue between repository and operational enviorment
Gaurav Chadha
Gaurav Chadha3w ago
we'll check on delays though, in the video https://jam.dev/c/8a18c092-68c5-4e7e-b49a-042e65b684cb. You didn't let the the test to complete execution, it is still in running state, after the running state is completed and you click refresh it does show up. We'll check on this to display it in a better UX. Thanks.
oneway6026
oneway60263w ago
No, it is finished, at the 0:23 you got the result If you need help, let me know. I am willing to check it out, free of charge Hello Gaurav, any update on this one?
Gaurav Chadha
Gaurav Chadha3w ago
We are working on fixing the issue, yes you are right, its not with the logging, but with syncing on production.