Welcome! Log In Create A New Profile

Advanced

Re: Worker ID

Maxim Dounin
May 15, 2014 08:14AM
Hello!

On Wed, May 14, 2014 at 09:10:04PM -0400, Jordan Newman wrote:

> 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.

For this use case it should be fine to use just a process id of a
worker. It's as available in the ngx_pid global variable (and as
the $pid nginx variable).

--
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

Worker ID

Jordan Newman 829 May 13, 2014 09:22PM

Re: Worker ID

wandenberg 563 May 13, 2014 10:52PM

Re: Worker ID

Maxim Dounin 415 May 14, 2014 10:56AM

Re: Worker ID

Jordan Newman 587 May 14, 2014 09:12PM

Re: Worker ID

Maxim Dounin 405 May 15, 2014 08:14AM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 211
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready