This Joyent page also has a lot of valuable information about debugging Node, with a bias towards production environments and using SmartOS:
http://www.joyent.com/developers/node/debug There was a lot of material on this page I found valuable. On Sun, Jan 19, 2014 at 11:40 AM, Daniel Rinehart <dani...@neophi.com>wrote: > Some of the information is getting a little dated but slides from a talk I > gave last year about debugging can be found at: > > http://life.neophi.com/danielr/files/DebuggingNodejsApplications.pdf > > A few of the tools mentioned, and which I've used on various projects, > include: > > Better logging: built in console, debug module, winston module, bunyan > module > Debugging: built in debugger, node inspector > Speed performance: built in console, statsd module, tick module > Memory performance: memwatch module, v8 profiler > Others: nodetime module, new relic, dtrace, webstorm > > > -- Daniel R. <dani...@neophi.com> [http://danielr.neophi.com/] > > > On Sun, Jan 19, 2014 at 11:37 AM, wavded <wav...@gmail.com> wrote: > >> Hey everybody, doing a bit of research here and wondering if you can help >> me out! >> >> I personally have benefitted the most from logging, node-webkit-agent >> module (perf/memleaks), heapdump module (for prod memleaks), and strace (on >> linux) when it comes to debugging Node applications. However, I'm sure >> there are tools I haven't used much or had use cases for personally that >> are dynamite (like dtrace for instance). I'm curious as to what >> tools/techniques you have used AND for what situations were they helpful. >> No bad answers here so don't be shy :) >> >> Thanks much! >> Marc >> >> -- >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to nodejs@googlegroups.com >> To unsubscribe from this group, send email to >> nodejs+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to nodejs+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nodejs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
