Azure NGINXaaS monitoring configuration
Site24x7's Azure NGINXaaS (NGINX as a Service) monitoring feature enables you to track performance, capacity utilization, connection metrics, and HTTP request analytics of your Azure NGINXaaS resources. With comprehensive real-time insights, you can ensure optimal web server performance, monitor traffic patterns, and maintain high availability for your applications.
Key features
Site24x7's Azure NGINXaaS monitoring integration supports:
- Capacity monitoring: Track NCU (NGINX Compute Units) provisioned, requested, and capacity percentage to optimize resource allocation.
- Connection analytics: Monitor active, idle, and current connections along with connection acceptance and drop rates.
- HTTP performance tracking: Comprehensive HTTP request and response monitoring with status code breakdown and rate limiting metrics.
- Security insights: Monitor WAF (Web Application Firewall) status, SSL handshakes, and certificate management.
- System performance: Track worker connections, listener backlog, and port utilization for optimal system performance.
- Root Cause Analysis: Receive alerts when performance thresholds are exceeded or security issues are detected.
Setup and configuration
You can add Azure NGINXaaS services while adding a new monitor, or you can add it to an existing Azure monitor. Follow these steps to add the service.
Supported metrics
The following metrics are collected:
| Metric name | Description | Statistic | Unit |
|---|---|---|---|
| NCU Provisioned | The number of NGINX Compute Units (NCUs) provisioned for the NGINXaaS instance. | Maximum | Count |
| NCU Requested | The number of NGINX Compute Units (NCUs) currently requested by the NGINXaaS instance. | Average | Count |
| NGINXaaS Capacity Percentage | The percentage of NGINXaaS capacity currently being utilized. | Average | Percentage |
| System Worker Connections | The number of worker connections available in the system for handling requests. | Maximum | Count |
| NGINXaaS Certificates | The number of SSL/TLS certificates configured for the NGINXaaS instance. | Maximum | Count |
| NGINXaaS MaxMind | Status of MaxMind GeoIP database integration for geographic request analysis. | Latest | State |
| WAF Enabled | Indicates whether Web Application Firewall (WAF) is enabled and active. | Latest | Boolean |
| System Listener Backlog Max | The maximum number of connections that can be queued in the system listener backlog. | Maximum | Count |
| System Listener Backlog Queue Limit | The configured limit for the system listener backlog queue. | Maximum | Count |
| System Listener Backlog Length | The current length of the system listener backlog queue. | Average | Count |
| Ports Used | The number of network ports currently in use by the NGINXaaS instance. | Average | Count |
| NGINX Connections Accepted | The total number of client connections accepted by NGINX. | Total | Count |
| NGINX Connections Dropped | The total number of client connections dropped by NGINX. | Total | Count |
| NGINX Active Connections | The current number of active client connections being processed by NGINX. | Average | Count |
| NGINX Idle Connections | The current number of idle client connections maintained by NGINX. | Average | Count |
| NGINX Current Connections | The total number of current client connections to NGINX (active + idle). | Average | Count |
| NGINX HTTP Request Count | The total number of HTTP requests processed by NGINX. | Total | Count |
| NGINX Current HTTP Requests | The current number of HTTP requests being processed by NGINX. | Average | Count |
| NGINX HTTP Limit Connections Passed | The number of connections that passed through HTTP connection limiting rules. | Total | Count |
| NGINX HTTP Limit Connections Rejected | The number of connections rejected by HTTP connection limiting rules. | Total | Count |
| NGINX HTTP Limit Connections Rejected Dry Run | The number of connections that would be rejected in dry run mode for connection limiting. | Total | Count |
| NGINX HTTP Limit Requests Passed | The number of HTTP requests that passed through request rate limiting rules. | Total | Count |
| NGINX HTTP Limit Requests Delayed | The number of HTTP requests delayed by request rate limiting rules. | Total | Count |
| NGINX HTTP Limit Requests Rejected | The number of HTTP requests rejected by request rate limiting rules. | Total | Count |
| NGINX HTTP Limit Requests Delayed Dry Run | The number of HTTP requests that would be delayed in dry run mode for rate limiting. | Total | Count |
| NGINX HTTP Limit Requests Rejected Dry Run | The number of HTTP requests that would be rejected in dry run mode for rate limiting. | Total | Count |
| HTTP Request Count | The total number of HTTP requests received by the server. | Total | Count |
| HTTP Response Count | The total number of HTTP responses sent by the server. | Total | Count |
| HTTP Status 1xx | The number of HTTP responses with 1xx status codes (informational responses). | Total | Count |
| HTTP Status 2xx | The number of HTTP responses with 2xx status codes (successful responses). | Total | Count |
| HTTP Status 3xx | The number of HTTP responses with 3xx status codes (redirection responses). | Total | Count |
| HTTP Status 4xx | The number of HTTP responses with 4xx status codes (client error responses). | Total | Count |
| HTTP Status 5xx | The number of HTTP responses with 5xx status codes (server error responses). | Total | Count |
| HTTP Status Processing | The number of HTTP requests currently being processed by the server. | Average | Count |
| HTTP Request Bytes Received | The total number of bytes received in HTTP requests. | Total | Bytes |
| HTTP Request Bytes Sent | The total number of bytes sent in HTTP responses. | Total | Bytes |
| HTTP Location Zone Request Count | The number of HTTP requests processed by specific location zones. | Total | Count |
| HTTP Location Zone Response Count | The number of HTTP responses sent by specific location zones. | Total | Count |
| HTTP Location Zone Status 1xx | The number of 1xx status responses from specific location zones. | Total | Count |
| HTTP Location Zone Status 2xx | The number of 2xx status responses from specific location zones. | Total | Count |
| HTTP Location Zone Status 3xx | The number of 3xx status responses from specific location zones. | Total | Count |
| HTTP Location Zone Status 4xx | The number of 4xx status responses from specific location zones. | Total | Count |
| HTTP Location Zone Status 5xx | The number of 5xx status responses from specific location zones. | Total | Count |
| HTTP Location Zone Status Processing | The number of requests currently being processed by specific location zones. | Average | Count |
| HTTP Location Zone Request Bytes Received | The total bytes received in requests by specific location zones. | Total | Bytes |
| HTTP Location Zone Request Bytes Sent | The total bytes sent in responses by specific location zones. | Total | Bytes |
| SSL Failed | The number of failed SSL/TLS handshake attempts. | Total | Count |
| SSL Handshakes | The total number of successful SSL/TLS handshakes completed. | Total | Count |
| SSL Reuses | The number of SSL/TLS session reuses for improved performance. | Total | Count |
| SSL No Common Protocol | The number of SSL/TLS connection failures due to no common protocol. | Total | Count |
Configuration details
Azure NGINXaaS monitoring provides comprehensive insights into:
- Resource utilization: Monitor NCU provisioning and capacity to ensure adequate resources for your workloads.
- Connection management: Track connection patterns, acceptance rates, and connection limits to optimize performance.
- HTTP analytics: Detailed breakdown of request/response patterns, status codes, and traffic volume.
- Security monitoring: SSL/TLS performance tracking and WAF status monitoring for enhanced security posture.
- Rate limiting: Monitor the effectiveness of rate limiting rules and their impact on traffic flow.
Threshold configuration
Associating a threshold profile can be done from the monitor's Edit page:
- Under Configuration Profiles > Threshold and Availability > select the corresponding threshold profile from the drop-down.
The changes made to this threshold profile will be applied to all the associated monitors. You can either add or edit a threshold profile by clicking the plus icon + or pencil icon
Bulk Action
Bulk association of threshold profiles can be done from the Admin page (Admin > Inventory > Bulk Action > under Monitor Configuration, go to Modify Threshold Profile).
You can set threshold values for the metrics by selecting the Threshold and Availability option. You can also configure IT automation at the attribute level.
IT automation
Site24x7 offers a set of exclusive IT automation tools to auto-resolve performance degradation issues. These tools react to events proactively rather than waiting for manual intervention.
How to configure IT automation for a monitor
Configuration Rules
With Site24x7's Configuration Rules, you can set parameters like Threshold Profile, Notification Profile, Tags, and Monitor Group for multiple monitors. These rules can be configured and run for the existing or new monitors (during addition) matching the given criteria.
How to add a configuration rule