You can find an annotated example of a config file for an NGINX Plus status module here. A sample NGINX Plus status board is available here.
ARBURG COPY LOG 5.0 CODE
NGINX Plus also reports counts of all HTTP status code types (1xx, 2xx, 3xx, 4xx, 5xx). Among the additional metrics exposed by NGINX Plus are bytes streamed, as well as information about upstream systems and caches. The commercial NGINX Plus provides many more metrics through its ngx_http_api_module than are available in open source NGINX. Parsers for the NGINX status page already exist for monitoring tools such as Nagios and Datadog, as well as for the statistics collection daemon collectD. The NGINX status page is an easy way to get a quick snapshot of your metrics, but for continuous monitoring you will need to automatically record that data at regular intervals. Note that if you are trying to access the status page from a remote machine, you will need to edit your status configuration to allow the remote machine’s IP address, just as 127.0.0.1 is allowed in the configuration snippet above. You can use the -with-http_stub_status_module configuration parameter when building NGINX from source: If that command returns no output, you will need to enable the status module. The status module is enabled if you see with-http_stub_status_module as output in the terminal. To check if the module is already enabled, run: nginx -V 2>&1 | grep -o with-http_stub_status_module Open source NGINX exposes several basic metrics about server activity on a simple status page, provided that you have the HTTP stub status module enabled. (See the companion article for an in-depth exploration of NGINX metrics.) Free, open source NGINX and the commercial product NGINX Plus both have status modules that report metrics, and NGINX can also be configured to report certain metrics in its logs: Metric
How you go about capturing metrics depends on which version of NGINX you are using, as well as which metrics you wish to access.
0 kommentar(er)
