Follow your code: Node/V8 tracing
A large percentage of Node application misbehavior can be effectively diagnosed through in-built Node/V8 tracing capabilities. There are a number of powerful tracing options to leverage in development, testing and production phases to validate that application design is indeed reflected in code, without ever instrumenting it.
I will illustrate "top 10" Node/V8 tracing options - from simplest method tracing (find out call sequences, input parameters, return values) to tuning specific JIT compiler options to diagnose and resolve complex crashes/issues. The intention is to help audience understand in-built serviceability features of Node Runtime Environment, and self help in resolving production anomalies.
Outline/Structure of the Talk
High level runtime environment view of Node/V8
High level overview of in-built tracing
Vital Node / V8 data structures
Major serviceabiulity symptoms/areas
Major tracing options mapping to symptoms
Example use case , usage and sample output of traces