craft icon indicating copy to clipboard operation
craft copied to clipboard

Store debug logs to disk

Open jan-auer opened this issue 7 years ago • 0 comments

I would prefer to run craft without debug logs on the console. Especially when publishing to crates.io, the output is enormously large. When errors occur, it would still be great to have debug logs around - sometimes with even more information than what debug currently logs.

Would it be an option to create a file like craft-debug.log in the cwd and delete it upon successful completion. This way, we can easily attach debug logs to bug reports.

Besides, it might be nice to have @sentry/node in craft and log everything that goes into the error stream, maybe even attach previous logs as breadcrumbs (automatically done with the "console" integration).

jan-auer avatar Aug 30 '18 06:08 jan-auer