29a170617f
nginx_ingress_controller_nginx_process_connections returns four elements for each pod, one for each "state" (active, reading, waiting, writing). The value of the element with state "active" is the sum of the other three elements of other states: active = reading + waiting + writing So sum() returns a value that is 2x of the actual amount of connections. To fix this we simply select elements with state "active". |
||
|---|---|---|
| .. | ||
| .markdownlint.json | ||
| nginx.json | ||
| README.md | ||
| request-handling-performance.json | ||
| request-handling.png | ||
| screenshot.png | ||
Grafana Dashboards
Ingress-nginx supports a rich collection of prometheus metrics. If you have prometheus and grafana installed on your cluster then prometheus will already be scraping this data due to the scrape annotation on the deployment.
This folder contains two dashboards that you can import.
1. NGINX Ingress Controller
Features
- Ability to filter by Namespace, Controller Class and Controller
- Visibility of Request Volume, connections, success rates, config reloads and configs out of sync.
- Network IO pressure, memory and CPU use
- Ingress P50, P95 and P99 percentile response times with IN/OUT throughput
- SSL certificate expiry
- Annotational overlays to show when config reloads happened
Requirements
- Grafana v5.2.0 (or newer)
2. Request Handling Performance
Features
- Ability to filter by Ingress
- P50, P95 and P99 percentile of total request and upstream response times
- Request volume by path
- Error volume and error rate by path
- Average response time by path
- ...and more
Requirements
- Grafana v6.6.0 (or newer)