Skip to content

Commit 5a8fff1

Browse files
technovangelisttechnovangelist
committed
update nginx to reflect csv showing all metrics
1 parent c720df5 commit 5a8fff1

File tree

1 file changed

+14
-55
lines changed

1 file changed

+14
-55
lines changed

‎content/integrations/nginx.md

Lines changed: 14 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -40,10 +40,23 @@ If you see some output with `configure arguments:` and lots of options, then you
4040
For more information on configuration, read the [stub status docs](http://nginx.org/en/docs/http/ngx_http_stub_status_module.html). For some more insight into configuring the agent, check out the [NGINX example YAML config](https://github.com/DataDog/dd-agent/blob/master/conf.d/nginx.yaml.example) or take a look at the [NGINX agent plugin](https://github.com/DataDog/dd-agent/blob/master/checks.d/nginx.py).
4141

4242

43-
**Metrics collected by default via stub status module**
43+
**All metrics collected for NGINX and NGINX Plus**
4444

4545
<%= get_metrics_from_git()%>
4646

47+
#### NGINX (Open Source)
48+
49+
| Metrics collected in NGINX ||
50+
|--------------------------|----|
51+
| <strong>nginx.net.writing</strong><br/>(gauge) | The number of connections waiting on upstream responses and/or writing responses back to the client <br/>shown as connection|
52+
| <strong>nginx.net.waiting</strong><br/>(gauge)| The number of keep-alive connections waiting for work<br/>shown as connection|
53+
| <strong>nginx.net.reading</strong><br/>(gauge)| The number of connections reading client requets<br/>shown as connection|
54+
| <strong>nginx.net.connections</strong><br/>(gauge)| Total number of active connections<br/>shown as connection|
55+
| <strong>nginx.net.request_per_s</strong><br/>(rate)| Number of requests processed per second<br/>shown as request/second|
56+
| <strong>nginx.net.conn_opened_per_s</strong><br/>(rate)| Number of connections opened per second<br/>shown as connection/second|
57+
| <strong>nginx.net.conn_dropped_per_s</strong><br/>(rate)| Number of connections dropped per second<br/>shown as connection/second|
58+
{:.table}
59+
4760
The data pulled from the nginx stub status page are described in the [NGINX docs](http://nginx.org/en/docs/http/ngx_http_stub_status_module.html#data).
4861

4962
#### NGINX Plus
@@ -76,59 +89,5 @@ Finally, these metrics have no good translation:
7689
| nginx.net.writing | The current number of connections where nginx is writing the response back to the client. |
7790
{:.table}
7891

79-
<br/>
80-
81-
| Other metrics collected in NGINX Plus |
82-
|--------------------------|
83-
| nginx.connections.accepted | The total number of accepted client connections.|
84-
| nginx.connections.active |The current number of active client connections.|
85-
| nginx.connections.dropped |The total number of dropped client connections.|
86-
| nginx.connections.idle |The current number of idle client connections.|
87-
| nginx.generation | The total number of configuration reloads.|
88-
| nginx.load_timestamp | Time of the last reload of configuration, in milliseconds since Epoch.|
89-
| nginx.pid | The ID of the worker process that handled status request.|
90-
| nginx.processes.respawned |The total number of abnormally terminated and respawned child processes.|
91-
| nginx.requests.current | The current number of client requests.|
92-
| nginx.requests.total |The total number of client requests.|
93-
| nginx.server_zone.discarded |The total number of requests completed without sending a response.|
94-
| nginx.server_zone.processing |The number of client requests that are currently being processed.|
95-
| nginx.server_zone.received |The total number of bytes received from clients.|
96-
| nginx.server_zone.requests |The total number of client requests received from clients.|
97-
| nginx.server_zone.responses.1xx |The number of responses with 1xx status code.|
98-
| nginx.server_zone.responses.2xx |The number of responses with 2xx status code.|
99-
| nginx.server_zone.responses.3xx |The number of responses with 3xx status code.|
100-
| nginx.server_zone.responses.4xx |The number of responses with 4xx status code.|
101-
| nginx.server_zone.responses.5xx |The number of responses with 5xx status code.|
102-
| nginx.server_zone.responses.total |The total number of responses sent to clients.|
103-
| nginx.server_zone.sent |The total number of bytes sent to clients.|
104-
| nginx.ssl.handshakes |The total number of successful SSL handshakes.|
105-
| nginx.ssl.handshakes_failed |The total number of failed SSL handshakes.|
106-
| nginx.ssl.session_reuses |The total number of session reuses during SSL handshake.|
107-
| nginx.timestamp |Current time in milliseconds since Epoch.|
108-
| nginx.upstream.keepalive |The current number of idle keepalive connections.|
109-
| nginx.upstream.peers.active |The current number of active connections.|
110-
| nginx.upstream.peers.backup |A boolean value indicating whether the server is a backup server.|
111-
| nginx.upstream.peers.downstart |The time (in milliseconds since Epoch) when the server became “unavail” or “unhealthy”.|
112-
| nginx.upstream.peers.downtime |Total time the server was in the “unavail” and “unhealthy” states.|
113-
| nginx.upstream.peers.fails |The total number of unsuccessful attempts to communicate with the server.|
114-
| nginx.upstream.peers.health_checks.checks |The total number of health check requests made.|
115-
| nginx.upstream.peers.health_checks.fails |The number of failed health checks.|
116-
| nginx.upstream.peers.health_checks.last_passed |Boolean indicating if the last health check request was successful and passed tests.|
117-
| nginx.upstream.peers.health_checks.unhealthy |How many times the server became unhealthy (state “unhealthy”).|
118-
| nginx.upstream.peers.id |The ID of the server.|
119-
| nginx.upstream.peers.received |The total number of bytes received from this server.|
120-
| nginx.upstream.peers.requests |The total number of client requests forwarded to this server.|
121-
| nginx.upstream.peers.responses.1xx |The number of responses with 1xx status code.|
122-
| nginx.upstream.peers.responses.2xx |The number of responses with 2xx status code.|
123-
| nginx.upstream.peers.responses.3xx |The number of responses with 3xx status code.|
124-
| nginx.upstream.peers.responses.4xx |The number of responses with 4xx status code.|
125-
| nginx.upstream.peers.responses.5xx |The number of responses with 5xx status code.|
126-
| nginx.upstream.peers.responses.total |The total number of responses obtained from this server.|
127-
| nginx.upstream.peers.selected |The time (in milliseconds since Epoch) when the server was last selected to process a request (1.7.5).|
128-
| nginx.upstream.peers.sent |The total number of bytes sent to this server.|
129-
| nginx.upstream.peers.unavail |How many times the server became unavailable for client requests (state “unavail”) due to the number of unsuccessful attempts reaching the max_fails threshold.|
130-
| nginx.upstream.peers.weight |Weight of the server.|
131-
| nginx.version | Version of nginx. |
132-
{:.table}
13392

13493
The data pulled from the NGINX Plus status page are described in the [NGINX docs](http://nginx.org/en/docs/http/ngx_http_status_module.html#data).

0 commit comments

Comments
 (0)