NGINX OpenTelemetry Assets

The NGINX OpenTelemetry Assets package allows you to monitor Nginx, a high-performance web server, reverse proxy, and load balancer. NGINX is widely used for serving web content, proxying traffic, and load balancing across multiple servers.

This content package provides dashboards, alerting rule templates, and SLO templates for NGINX metrics and logs collected by the Nginx (OpenTelemetry) integration package: stub_status metrics from the NGINX receiver, and access and error logs parsed from the NGINX log files.

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

1. NGINX with the stub_status module enabled and the status endpoint reachable by Elastic Agent. For example:

server {
    listen 80;
    server_name localhost;
    location /nginx_status {
        stub_status on;
        allow 127.0.0.1;
        deny all;
    }
}
		

2. Install the Nginx (OpenTelemetry) integration package and configure it with your stub_status endpoint and the paths of your NGINX access and error logs. The dashboards and templates rely on the fields that integration parses from the logs (for example url.path, http.response.status_code, and log.level), so collect the data through it rather than a custom Collector configuration.

3. Optional: to populate the latency panels, configure the extended NGINX log format with request and upstream timings described in the Nginx (OpenTelemetry) integration package documentation.

This package includes four pre-built Kibana dashboards:

• [Nginx OTel] Overview — All NGINX instances at a glance: golden-signal KPIs, request rate, error rate and latency trends, an instance hexmap and table, error-log analysis, and top instances over time. Drill down from an instance to its details.
• [Nginx OTel] Request Health — Latency (P50/P95/P99, upstream vs NGINX time, slowest URL paths), 4xx/5xx errors, and error logs.
• [Nginx OTel] Server Internals — Connection states, accepted vs handled connections, request throughput, and per-instance stub_status metrics.
• [Nginx OTel] Traffic & Capacity — Request volume, bytes served, top URL paths, clients, user agents, HTTP methods and protocol versions, plus peak capacity.

Request Health, Server Internals, and Traffic & Capacity share a tab bar and keep the instance selected on the Overview.

This package ships five alerting rule templates that you can enable and customize:

All rules use ES|QL queries, run every 1 minute, and group by host.name. Thresholds can be adjusted to match your environment's baseline.

This package includes two SLO templates:

Both SLOs are grouped by host.name, allowing per-instance tracking.

The dashboards use the stub_status metrics collected by the NGINX receiver. For the full list of metrics and their attributes, refer to the NGINX receiver documentation in the upstream OpenTelemetry Collector repository.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.

← →

×

×

×

×