Thanks, ngx_process_slot was what I needed. The reason for knowing the worker
# is for stat tracking, its important that the backend where the stats are
being collected on knows to group them together by worker and then by server.
--
Jordan Newman
> On May 14, 2014, at 10:55 AM, Maxim Dou
Is there a way from an nginx module to see which # worker it is? Thank you.
--
Jordan Newman
___
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
. I was planning on
setting up a write event and then doing math to see how much data has been
written to the socket to fill it each time but I am open to other suggestions
as well. Any advice you can provide would be greatly appreciated. Thanks in
advance for your help.
--
Jordan Newman
