Skip to main content

NGINX monitoring

NGINX is a web server which can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

This module will monitor one or more NGINX servers, depending on your configuration.

Requirements#

Charts#

It produces following charts:

  • Active Client Connections Including Waiting Connections in connections
  • Active Connections Per Status in connections
  • Accepted And Handled Connections in connections/s
  • Requests in requests/s

Configuration#

Edit the go.d/nginx.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/nginx.conf

Needs only url to server's stub_status. Here is an example for local and remote servers:

jobs:
- name: local
url: http://127.0.0.1/stub_status
- name: remote
url: http://203.0.113.10/stub_status

For all available options please see module configuration file.

Troubleshooting#

To troubleshoot issues with the nginx collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

First, navigate to your plugins directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch to the netdata user.

cd /usr/libexec/netdata/plugins.d/
sudo -u netdata -s

You can now run the go.d.plugin to debug the collector:

./go.d.plugin -d -m nginx

Reach out

If you need help after reading this doc, search our community forum for an answer. There's a good chance someone else has already found a solution to the same issue.

Documentation

Community

Last updated on