[Erlang危机](5.0)执行时指标

原创文章。转载请注明出处：server非业余研究http://blog.csdn.net/erlib 作者Sunface

. 
 Then, in times of need, it’s also possible to bypass the tools and go direct to the VM for information.

。

甚至在须要时，直接向VM获取信息(无需使用工具)。 A practical approach to growing a system and keeping it healthy in production is to make sure all angles are observable: in the large, and in the small. There’s no generic recipe to tell in advance what is going to be normal or not.
 You want to keep a lot of data and to look at it from time to time to form an idea about what your system looks like under normal circumstances. The day something goes awry, you will have all these angles you’ve grown to know, and it will be simpler to find what is off and needs fixing. library, and are generally production-safe.库里。他们都是能够放心使用的。[1] Making sure your automated processes don’t run away and go overboard with whatever corrective actions they take is more complex
[2] http://ferd.github.io/recon/[注1]：确保你的自己主动化过程不走极端，不跑偏。
[注2]：http://ferd.github.io/recon/。