15 NGINX Metrics to Monitor
summary
Open source NGINX exposes roughly 10 metrics via the status module (active connections, request rate, request_time, upstream response time, error rates, handshake time, throughput, blocked requests, cache hit ratio), while NGINX Plus surfaces about 138 metrics plus a built-in dashboard. Prometheus scraping and OpenTelemetry tracing are supported; the native OpenTelemetry module adds about ~10% CPU overhead versus ~50% for the community tracer. Examples include detecting traffic spikes, gradual load increases, security blocked-request spikes, and tuning cache hit ratios.
AI-written summary · about
chapters (9)
- 0:00Introduction and Speaker Background
- 1:03Overview of NGINX
- 1:22Monitoring and Metrics Essentials
- 1:58Open Source vs. NGINX Plus
- 4:31Key Metrics Explained
- 13:38Analyzing Traffic Patterns
- 17:05Security and Error Monitoring
- 20:05Open Telemetry and Prometheus Integration
- 23:41Conclusion and Q&A
related talks
06mAgentic Observability With NGINX: Open Source MCP Traffic Monitoring
19mWhat You Need to Know About OpenMetrics
31mEvolution of Metric Monitoring and Alerting: Upgrade Your Prometheus Today
21mCommon NGINX Misconfigurations That Leave Your Web Server Open ...
36mMetrics - What's your code actually doing?
37mCloud-native Metric Monitoring with Prometheus
27mEasy App Metrics
58mHow to tune Nginx to survive a DDoS