User Journey tracking documentation

[RafaelGSS]

This issue aims to track the remaining tutorials under documentation folder.

The #439 contains the documents created in the WG Deep Dive and we are working to transpose them into live documents.

• Abnormal Termination
  • Using exit stack traces
  • Using diagnotics report
  • Using valgrind
  • Using llnode
• CPU
  • Monitoring Excessive CPU Usage
• Crash
  • What is a crash (intro)
  • Using node report
  • Using llnode (Document User Journey llnode#401)
• Hang
  • Using trace sigint
  • Using Chrome DevTools
  • Using node report
• Live Debugging (guide: add user journey live debugging document nodejs.org#4772)
  • Using Node Inspector
• Memory (guide: add user journey memory tutorial nodejs.org#4728)
  • Using Heap Profiler
  • Using Heap Snapshot
  • Using GC Traces
  • Using Native Tools
• Poor Performance (doc: include poor-performance diagnostic nodejs.org#4928)
  • Using V8 Profiler
  • Using Linux Perf
• Tracing
  • Using Trace Events

Feel free to update this description when a tutorial is done.

cc: @nodejs/diagnostics

[RafaelGSS]

What we are supposed to do in the CPU journey? It looks pretty similar to what we did in Profiling.

[mhdawson]

@RafaelGSS a few thoughts:

1. The goal was to be based on a user journey (ie problem->resolution) versus tool based. In that context we should probably rename "Profiling" to "Poor Performance".
2. CPU should then likely be "Excessive CPU usage". The symptoms would be different (ie performance could be fine, but you may be using more CPU than expected/wanted). The Debugging might then be the same as figuring out where CPU is used will be the same between the 2.

[RafaelGSS]

Excellent, I agree.

[RafaelGSS]

I'm adding it to the agenda to discuss how we can expose it to the community in a call for help. Maybe a tweet could be enough?

[github-actions]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.