doc: add abnormal termination step 1 #344
Conversation
legendecas
force-pushed
the
abnormal-exit
branch
from
63da600
to
b054c98
Compare
|
We probably need more info in this section as well as we should explain how you can use the stack traces for debugging. |
| @@ -1 +1,15 @@ | |||
| //TODO | |||
| # Using `--trace-exit` CLI Option | |||
There was a problem hiding this comment.
| # Using `--trace-exit` CLI Option | |
| # Using Exit Stack Traces for Debugging | |
| //TODO | |
| # Using `--trace-exit` CLI Option |
|
@mhdawson PTAL again :D |
| ``` | ||
|
|
||
| With the knowledge of where the calls of `process.exit` is, we can check around | ||
| the invocation to guess the reasons and prevent it from abnormal exits. |
There was a problem hiding this comment.
I'm not a huge fan of using the word guess here. The whole point of using instrumentation is to empower users to make informed decisions instead of guessing why things are not working.
| the invocation to guess the reasons and prevent it from abnormal exits. | |
| the invocation to understand the reasons and prevent it from abnormal exits. |
| With the knowledge of where the calls of `process.exit` is, we can check around | ||
| the invocation to guess the reasons and prevent it from abnormal exits. | ||
|
|
||
| Or if we find there is no such prints on process exits, we can come to a |
There was a problem hiding this comment.
| Or if we find there is no such prints on process exits, we can come to a | |
| If the process doesn't output a stack trace on exit, we can come to a |
| the invocation to guess the reasons and prevent it from abnormal exits. | ||
|
|
||
| Or if we find there is no such prints on process exits, we can come to a | ||
| conclusion that the process may exited for some other obscure reasons, and we |
There was a problem hiding this comment.
| conclusion that the process may exited for some other obscure reasons, and we | |
| conclusion that the process exited for other reasons, and we |
|
|
||
| Or if we find there is no such prints on process exits, we can come to a | ||
| conclusion that the process may exited for some other obscure reasons, and we | ||
| have to deploy following steps of the Abnormal Termination guides. |
There was a problem hiding this comment.
, and we have to deploy following steps of the Abnormal Termination guides.
This is vague, I'd rather point the user to specific guides based on symptoms. Might be worth leaving that last part out or leaving a placeholder so we can replace it in the future when those guides are written.
Confirming if the process was exited for proactive invocation of `process.exit`.
legendecas
force-pushed
the
abnormal-exit
branch
from
0a0df4f
to
a3b9520
Compare
Confirming if the process was exited for proactive invocation of
process.exit.The option is available after nodejs/node#30516 has been landed.