Skip to content
Discussions/App Development/Debugging DAML when in NavigatorForum ↗

Debugging DAML when in Navigator

App Development6 posts631 views5 likesLast activity Aug 2020
JE
Jean_SafarOP
Aug 2020

How do you inspect the error stack in Navigator? I can see the error logo displayed but I can’t get to the reason… apologies if really basic … but can’t find that in the doc …

CO
cocreature
Aug 2020

Navigator writes out a log file called navigator.log. That contains the error I believe. I’m not sure if you can see the details directly in the browser.

JE
Jean_Safar
Aug 2020

Thanks for that. I was starting to look at that and it gives me some clues … do I have a way to increase the log level?.

CO
cocreature
Aug 2020

You could in principle use a custom logback config file similar to how you can for sandbox How can I make debug statements visible in the sandbox logs?. However, that isn’t going to show you more information for a failed transaction afaict. All the relevant logs are already logged at error level.

BE
bernhard
Aug 2020

In many cases the Ledger (eg Sandbox) logs more information about failed transactions than is returned via the Ledger API. The Ledger API can only give information that can’t cause privacy leaks, after all.

So it can be very useful to also check sandbox.log.

CO
cocreature
Aug 2020

Note that you need at least --log-level info to see failed commands in the sandbox log iirc.

← Back to Discussions