Please help review and approve one change

[Maxim Dounin]

Hello!

On Wed, Dec 20, 2017 at 03:15:24PM +0800, Xiaohua Wang wrote:

> Added to trace HTTP request call flow in nginx.
> 
> Especially for performance or load test purpose.
> Because info level log is not enough,
> and debug log is too much which impacts performance a lot.
> Currently, two scenarios are supported.
> 1) trace any point in source code like before/after function entry, or
> middle of function.
> 2) trace any call flow which takes longer time than specific latency
> between two check point.

> # HG changeset patch
> # User Xiaohua Wang <xiaohuaw at gmail.com>
> # Date 1513591776 -28800
> #      Mon Dec 18 18:09:36 2017 +0800
> # Node ID 1cf1d4a74783573da28793f39b924fa551fdfb65
> # Parent  d3235149d17f7745d3ac246a6cdcc81a56698f7b
> Added to trace http request call flow in nginx.
> 
> Especillay for performance or load test purpose.
> Because info level log is not enough,
> and debug log is too much which impacts performace a lot.
> 
> Currently, two scenarios are supported.
> 1) trace any piont in source code like before/after function entry, or middle of function.
> 2) trace any call flow which takes longer time than specific latency between two check point.

No, thanks.

If you need detailed real-time tracing, you may consider using 
DTrace.  The following article describes how to use it with nginx:

http://nginx.org/en/docs/nginx_dtrace_pid_provider.html

-- 
Maxim Dounin
http://mdounin.ru/