# Save debug Node into a file
**URL:** https://discourse.nodered.org/t/save-debug-node-into-a-file/46299
**Category:** General
**Created:** [26 May 2021 18:35 UTC](https://discourse.nodered.org/t/save-debug-node-into-a-file/46299 "2021-05-26T18:35:06Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@vikozo](https://discourse.nodered.org/u/vikozo)
#### Post date: [26 May 2021 18:35 UTC](https://discourse.nodered.org/t/save-debug-node-into-a-file/46299/1 "2021-05-26T18:35:06Z")
Hello
i have a flow and of course some debug node!
no the debug information comes not often - most in the night.
Is there a way to save the hole debug information into a file?
have a nice day
vinc
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [26 May 2021 18:36 UTC](https://discourse.nodered.org/t/save-debug-node-into-a-file/46299/2 "2021-05-26T18:36:48Z")
There are several options. A simple option is to use [flogger](https://flows.nodered.org/node/node-red-contrib-flogger) in place of or alongside debug nodes.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [27 May 2021 08:17 UTC](https://discourse.nodered.org/t/save-debug-node-into-a-file/46299/3 "2021-05-27T08:17:11Z")
If you set your debug node to output to the console then it will log it to the node red log. If you are using a linux system (such as on a pi) then it will go to /var/log/syslog so you can look at that file, or or you can use `journalctl` to look back at the node red log. I don't know where it goes on Windows. Alternatively, if you start node-red running in a terminal and leave the terminal open then it will be in there.
---
### Author:  [@vikozo](https://discourse.nodered.org/u/vikozo)
#### Post date: [27 May 2021 18:50 UTC](https://discourse.nodered.org/t/save-debug-node-into-a-file/46299/4 "2021-05-27T18:50:55Z")
@Colin merci found it - but it is not just the information from debug, but just all requests!
Maybe i will have to install @Steve-Mcl mentioned flogger - merci
vinc
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [27 May 2021 20:12 UTC](https://discourse.nodered.org/t/save-debug-node-into-a-file/46299/5 "2021-05-27T20:12:59Z")
You can pipe it through grep to find only the bits you are interested in. It depends what you are trying to do. If you are just trying to analyse a fault, for example, then that should be good enough, but if you are looking for more permanent logging for later analysis then a more sophisticated solution is probably worth the extra effort.
---
### Author:  [@vikozo](https://discourse.nodered.org/u/vikozo)
#### Post date: [28 May 2021 17:40 UTC](https://discourse.nodered.org/t/save-debug-node-into-a-file/46299/6 "2021-05-28T17:40:52Z")
@Steve-Mcl i installed flogger but i got a
cant write file
and yes i have it on a Raspi Linux
gruss
vinc
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [28 May 2021 17:51 UTC](https://discourse.nodered.org/t/save-debug-node-into-a-file/46299/7 "2021-05-28T17:51:48Z")
where did you try to write file?
config:
node:
Does the account that runs node-red have permissions to write to that areas?
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [27 July 2021 17:52 UTC](https://discourse.nodered.org/t/save-debug-node-into-a-file/46299/8 "2021-07-27T17:52:17Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.