Monitor self-hosted NGINX Plus with OpenTelemetry

Monitor your NGINX Plus servers running on a host using the NRDOT collector (recommended) or OpenTelemetry Collector to send metrics and telemetry data to New Relic.

This integration leverages the OpenTelemetry prometheusreceiver and nginx-prometheus-exporter to monitor your NGINX Plus performance metrics, connection statistics, and server health. The rich HTTP API in NGINX Plus provides significantly more detailed metrics compared to the basic stub status module in standard NGINX.

Dashboard available through the New Relic NGINX OpenTelemetry Monitor quickstart.

Before you begin

Ensure you have:

Valid New Relic license key
NGINX Plus version R13 or higher
NGINX Plus with the HTTP API module enabled
NGINX Prometheus exporter installed and running alongside your NGINX Plus instance to expose HTTP API metrics in Prometheus format
One of the following collectors installed on a Linux host:
- NRDOT collector (recommended - New Relic's OpenTelemetry distribution), or
- OpenTelemetry Collector Contrib (alternative option)
Network access from the Linux host to:
- NGINX Plus HTTP API endpoint
- A New Relic OTLP endpoint

Set up NGINX Plus monitoring

Choose your preferred collector and follow the configuration steps:

팁

If any verification step fails, install the missing components before continuing. Need help installing the NRDOT collector? Check the installation section of the nrdot-collector-releases repository.

During installation use export collector_distro="nrdot-collector"

Configure the NRDOT collector

Configure the NRDOT collector to scrape metrics from your NGINX Plus Prometheus exporter and send them to New Relic.

For NRDOT collector, create a standalone NGINX Plus monitoring configuration file that replaces the default configuration.

중요

Standalone vs. Combined monitoring: This configuration monitors NGINX Plus servers only. If you also need host metrics (CPU, memory, disk) or system logs, use the NRDOT collector's default configuration which includes the hostmetrics and filelog receivers, and add the prometheus receiver to it.

Create /etc/nrdot-collector/nginx-plus-config.yaml with the following content:

receivers:
  prometheus:
    config:
      scrape_configs:
        - job_name: 'nginx-plus'
          scrape_interval: 30s
          static_configs:
            - targets: ['<YOUR_PROMETHEUS_EXPORTER_ENDPOINT>']
processors:
  batch:
    send_batch_size: 1024
    timeout: 30s
  filter/nginx_metrics:
    metrics:
      include:
        match_type: regexp
        metric_names:
          - "nginxplus_connections_.*"
          - "nginxplus_http_requests_.*"
          - "nginxplus_ssl_.*"
      exclude:
        match_type: regexp
        metric_names:
          - "nginxplus_server_.*"
          - "nginxplus_location_zone_.*"
          - "nginxplus_cache_.*"
          - "nginxplus_stream_server_.*"
          - "nginxplus_upstream_.*"
          - "nginxplus_stream_upstream_.*"
          - "nginxplus_stream_zone_sync_zone_.*"
          - "nginxplus_resolver_.*"
          - "nginxplus_limit_request_.*"
          - "nginxplus_limit_connection_.*"
          - "nginxplus_stream_limit_connection_.*"
          - "nginxplus_worker_.*"
  resource/nginx:
    attributes:
      - key: nginx.server.endpoint
        value: "<YOUR_API_STATUS_ENDPOINT>"  # Replace with your endpoint
        action: insert
      - key: nginx.deployment.name
        value: "<DEPLOYMENT_NAME>"                    # Replace with your deployment server name
        action: insert
  resourcedetection:
    detectors: [system]
    system:
      resource_attributes:
        host.name:
          enabled: true
        host.id:
          enabled: true
  transform/nginx:
    metric_statements:
      - context: resource
        statements:
          - set(attributes["nginx.display.name"], Concat(["server", attributes["nginx.deployment.name"]], ":"))
      - context: resource
        statements:
          - delete_key(attributes, "service.name")
  transform/metadata_nullify:
    metric_statements:
      - context: metric
        statements:
          - set(description, "")
          - set(unit, "")
exporters:
  otlp_http:
    endpoint: ${env:YOUR_NEWRELIC_OTLP_ENDPOINT}
    headers:
      api-key: ${env:YOUR_NEW_RELIC_LICENSE_KEY}
service:
  pipelines:
    metrics/nginx:
      receivers: [prometheus]
      processors: [batch, filter/nginx_metrics, resourcedetection, resource/nginx, transform/nginx, transform/metadata_nullify]
      exporters: [otlp_http]

Configuration parameters

The following table describes the key configuration parameters:

Parameter	Description
`<YOUR_PROMETHEUS_EXPORTER_ENDPOINT>`	Replace with the prometheus exporter endpoint (for example '127.0.0.1:9113')
`<YOUR_API_STATUS_ENDPOINT>`	Replace with the api status endpoint of the NGINX Plus server (for example http:/127.0.0.1/api/9)
`<DEPLOYMENT_NAME>`	Replace with a unique deployment name for this NGINX Plus server (for example `production-web-01`, `staging-api`, `prod-lb-01`)
`scrape_interval`	Interval in seconds to collect metrics. The default value is set to `30s`
`send_batch_size`	Number of metrics to batch before sending. The default value is set to `1024`
`timeout`	Timeout in seconds to wait before sending batched metrics. The default value is set to `30s`

By default, the configuration collects only core metrics (connections, HTTP requests, and SSL). To enable additional metric categories:

Identify the metrics you want to enable from the metrics list below and note which category they belong to.
Move the corresponding metric prefix from exclude to include in the filter/nginx_metrics processor.
Example: Enable HTTP Server Zones metrics

Find this line in the exclude section:

filter/nginx_metrics:
  metrics:
    include:
    # existing include metrics
    exclude:
      match_type: regexp
      metric_names:
        - "nginxplus_server_.*"

Move it to the include section:

filter/nginx_metrics:
  metrics:
    include:
      match_type: regexp
      metric_names:
        - "nginxplus_connections_.*"
        - "nginxplus_http_requests_.*"
        - "nginxplus_ssl_.*"
        - "nginxplus_server_.*"  # Added to enable server zone metrics
    exclude:
      match_type: regexp
      metric_names:
        # Remove "nginxplus_server_.*" from here
        - "nginxplus_location_zone_.*"
        - "nginxplus_cache_.*"
        # ... rest of exclude list

Restart the collector after making changes:
bash
```
$sudo systemctl restart nrdot-collector.service
```

Configure environment and update config path

Update the NRDOT collector configuration to use your NGINX Plus config file and set the OTLP endpoint.

Determine your OTLP endpoint based on your New Relic region. See Configure endpoint, port, and protocol for the complete list of endpoints and supported ports for your region.

중요

Your license key was already configured in /etc/nrdot-collector/nrdot-collector.conf during installation. You only need to update the config file path and OTLP endpoint.

Update the collector configuration file:

bash

$export collector_distro="nrdot-collector"
$export otlp_endpoint="YOUR_NEWRELIC_OTLP_ENDPOINT"  # Replace with your region's endpoint
$
$# Update the config file path to point to nginx-plus-config.yaml
$sudo sed -i 's|OTELCOL_OPTIONS="--config=/etc/nrdot-collector/config.yaml"|OTELCOL_OPTIONS="--config=/etc/nrdot-collector/nginx-plus-config.yaml"|' /etc/${collector_distro}/${collector_distro}.conf
$
$# Add the OTLP endpoint
$echo "OTEL_EXPORTER_OTLP_ENDPOINT=${otlp_endpoint}" | sudo tee -a /etc/${collector_distro}/${collector_distro}.conf > /dev/null

(Optional) Forward NGINX logs

Extend your collector configuration to include access and error logs if you want log events alongside metrics.

Note the full paths to your NGINX access and error log files. Defaults are usually /var/log/nginx/access.log and /var/log/nginx/error.log.

Update /etc/nrdot-collector/nginx-plus-config.yaml to add a filelog receiver and log pipeline:

receivers:
  prometheus:
    # existing Prometheus receiver configuration
  filelog/nginx_access_logs:
    include:
      - /var/log/nginx/access.log
  filelog/nginx_error_logs:
    include:
      - /var/log/nginx/error.log

processors:
  batch:
    # existing settings
  filter/nginx_metrics:
    # existing settings
  resourcedetection:
    # existing settings
  resource/nginx:
    # existing settings
  transform/nginx_metrics:
    # existing settings
  transform/nginx_access_logs:
    log_statements:
      - context: resource
        statements:
          - set(attributes["nginx.display.name"], Concat(["server", attributes["nginx.deployment.name"]], ":"))
          - set(attributes["logtype"], "nginx")
  transform/nginx_error_logs:
    log_statements:
      - context: resource
        statements:
          - set(attributes["nginx.display.name"], Concat(["server", attributes["nginx.deployment.name"]], ":"))
          - set(attributes["logtype"], "nginx-error")

exporters:
  # existing exporter setup

service:
  pipelines:
    # Your existing metrics pipeline...

    # Add log pipelines
    logs/nginx-access:
      receivers: [filelog/nginx_access_logs]
      processors: [batch, resource/nginx, transform/nginx_access_logs]
      exporters: [otlp_http]
    logs/nginx-error:
      receivers: [filelog/nginx_error_logs]
      processors: [batch, resource/nginx, transform/nginx_error_logs]
      exporters: [otlp_http]

Grant the collector user read access to the log files:

bash

$sudo usermod -a -G adm nrdot-collector
$sudo chmod 644 /var/log/nginx/access.log
$sudo chmod 644 /var/log/nginx/error.log

Restart the collector to apply the changes:
bash
```
$sudo systemctl restart nrdot-collector
```

Start monitoring

Now that everything is configured, start the NRDOT collector and verify that data is flowing to New Relic.

Apply the configuration changes:

bash

$sudo systemctl daemon-reload
$sudo systemctl restart nrdot-collector.service

Verify the service is running:
bash
```
$sudo systemctl status nrdot-collector.service
```
Expected output: Active: active (running) with no recent errors

Check startup logs:

bash

$sudo journalctl -u nrdot-collector.service -n 20

Generate test traffic (to create metrics):

bash

$# Make a few requests to your NGINX Plus server
$curl http://localhost

Allow time for initial data to appear in New Relic, then access your NGINX dashboard to verify data collection.

팁

If any verification step fails, install the missing components before continuing. Need help installing the collector? Check the OpenTelemetry Collector installation guide.

Configure the OpenTelemetry Collector

Configure the OpenTelemetry Collector to scrape metrics from your NGINX Plus Prometheus exporter and send them to New Relic.

중요

Before editing: Back up your existing configuration: sudo cp /etc/otelcol-contrib/config.yaml /etc/otelcol-contrib/config.yaml.backup

Edit your collector configuration file (typically /etc/otelcol-contrib/config.yaml) and add the following sections. If you already have receivers, processors, or exporters sections, merge these with your existing configuration:

receivers:
  prometheus:
    config:
      scrape_configs:
        - job_name: 'nginx-plus'
          scrape_interval: 30s
          static_configs:
            - targets: ['<YOUR_PROMETHEUS_EXPORTER_ENDPOINT>']
processors:
  batch:
    send_batch_size: 1024
    timeout: 30s
  filter/nginx_metrics:
    metrics:
      include:
        match_type: regexp
        metric_names:
          - "nginxplus_connections_.*"
          - "nginxplus_http_requests_.*"
          - "nginxplus_ssl_.*"
      exclude:
        match_type: regexp
        metric_names:
          - "nginxplus_server_.*"
          - "nginxplus_location_zone_.*"
          - "nginxplus_cache_.*"
          - "nginxplus_stream_server_.*"
          - "nginxplus_upstream_.*"
          - "nginxplus_stream_upstream_.*"
          - "nginxplus_stream_zone_sync_zone_.*"
          - "nginxplus_resolver_.*"
          - "nginxplus_limit_request_.*"
          - "nginxplus_limit_connection_.*"
          - "nginxplus_stream_limit_connection_.*"
          - "nginxplus_worker_.*"
  resource/nginx:
    attributes:
      - key: nginx.server.endpoint
        value: "<YOUR_API_STATUS_ENDPOINT>"  # Replace with your endpoint
        action: insert
      - key: nginx.deployment.name
        value: "<DEPLOYMENT_NAME>"                    # Replace with your deployment name
        action: insert
  resourcedetection:
    detectors: [system]
    system:
      resource_attributes:
        host.name:
          enabled: true
        host.id:
          enabled: true
  transform/nginx:
    metric_statements:
      - context: resource
        statements:
          - set(attributes["nginx.display.name"], Concat(["server", attributes["nginx.deployment.name"]], ":"))
      - context: resource
        statements:
          - delete_key(attributes, "service.name")
  transform/metadata_nullify:
    metric_statements:
      - context: metric
        statements:
          - set(description, "")
          - set(unit, "")
exporters:
  otlp_http:
    endpoint: ${env:YOUR_NEWRELIC_OTLP_ENDPOINT}
    headers:
      api-key: ${env:YOUR_NEW_RELIC_LICENSE_KEY}
service:
  pipelines:
    metrics/nginx:
      receivers: [prometheus]
      processors: [batch, filter/nginx_metrics, resourcedetection, resource/nginx, transform/nginx, transform/metadata_nullify]
      exporters: [otlp_http]

Configuration parameters

The following table describes the key configuration parameters:

Parameter	Description
`<YOUR_PROMETHEUS_EXPORTER_ENDPOINT>`	Replace with the prometheus exporter endpoint (for example '127.0.0.1:9113')
`<YOUR_API_STATUS_ENDPOINT>`	Replace with the api status endpoint of the NGINX Plus server (for example http:/127.0.0.1/api/9)
`<DEPLOYMENT_NAME>`	Replace with a unique deployment name for this NGINX Plus server (for example `production-web-01`, `staging-api`, `prod-lb-01`)
`scrape_interval`	Interval to collect metrics. The default value is set to `30s`
`send_batch_size`	Number of metrics to batch before sending. The default value is set to `1024`
`timeout`	Maximum time to wait before sending a batch. The default value is set to `30s`
`nginx.display.name`	Display name format for NGINX server in New Relic (automatically generated as "server:`<DEPLOYMENT_NAME>`")

By default, the configuration collects only core metrics (connections, HTTP requests, and SSL). To enable additional metric categories like server zones, location zones, or cache metrics:

Identify the metrics you want to enable from the metrics list below. Note which category they belong to (e.g., HTTP Server Zones, Location Zones, Cache).

Move the corresponding metric prefix from exclude to include in the filter/nginx_metrics processor.

Example: Enable HTTP Server Zones metrics

Find this line in the exclude section:

filter/nginx_metrics:
  metrics:
    include:
    # existing include metrics
    exclude:
      match_type: regexp
      metric_names:
        - "nginxplus_server_.*"

Move it to the include section:

filter/nginx_metrics:
  metrics:
    include:
      match_type: regexp
      metric_names:
        - "nginxplus_connections_.*"
        - "nginxplus_http_requests_.*"
        - "nginxplus_ssl_.*"
        - "nginxplus_server_.*"  # Added to enable server zone metrics
    exclude:
      match_type: regexp
      metric_names:
        # Remove "nginxplus_server_.*" from here
        - "nginxplus_location_zone_.*"
        - "nginxplus_cache_.*"
        # ... rest of exclude list

Restart the collector after making changes:
bash
```
$sudo systemctl restart otelcol-contri.service
```

Set up authentication

Configure secure authentication so the OpenTelemetry Collector can send data to your New Relic account. This step sets up environment variables to keep your credentials secure.

Get your New Relic credentials:
- License Key: Get your license key from the API Keys UI page
- OTLP Endpoint: Use your region's endpoint from New Relic OTLP endpoints

Configure the credentials:

Create a systemd override directory:

bash

$export collector_distro="otelcol-contrib"
$sudo mkdir -p /etc/systemd/system/${collector_distro}.service.d

Create the environment configuration file:

bash

$cat <<EOF | sudo tee /etc/systemd/system/${collector_distro}.service.d/environment.conf
$[Service]
$Environment="NEWRELIC_OTLP_ENDPOINT=<`YOUR_NEWRELIC_OTLP_ENDPOINT>`"
$Environment="NEWRELIC_LICENSE_KEY=`<YOUR_NEW_RELIC_LICENSE_KEY>`"
$EOF

(Optional) Forward NGINX logs

Extend your collector configuration to include access and error logs if you want log events alongside metrics.

Note the full paths to your NGINX access and error log files. Defaults are usually /var/log/nginx/access.log and /var/log/nginx/error.log.

Update /etc/otelcol-contrib/config.yaml to add a filelog receiver and log pipeline:

receivers:
  prometheus:
    # existing Prometheus receiver configuration
  filelog/nginx_access_logs:
    include:
      - /var/log/nginx/access.log
  filelog/nginx_error_logs:
    include:
      - /var/log/nginx/error.log

processors:
  batch:
    # existing settings
  filter/nginx_metrics:
    # existing settings
  resourcedetection:
    # existing settings
  resource/nginx:
    # existing settings
  transform/nginx_metrics:
    # existing settings
  transform/nginx_access_logs:
    log_statements:
      - context: resource
        statements:
          - set(attributes["nginx.display.name"], Concat(["server", attributes["nginx.deployment.name"]], ":"))
          - set(attributes["logtype"], "nginx")
  transform/nginx_error_logs:
    log_statements:
      - context: resource
        statements:
          - set(attributes["nginx.display.name"], Concat(["server", attributes["nginx.deployment.name"]], ":"))
          - set(attributes["logtype"], "nginx-error")

exporters:
  # existing exporter setup

service:
  pipelines:
    # Your existing metrics pipeline...

    # Add log pipelines
    logs/nginx-access:
      receivers: [filelog/nginx_access_logs]
      processors: [batch, resource/nginx, transform/nginx_access_logs]
      exporters: [otlp_http]
    logs/nginx-error:
      receivers: [filelog/nginx_error_logs]
      processors: [batch, resource/nginx, transform/nginx_error_logs]
      exporters: [otlp_http]

Grant the otelcol-contrib user read access to the log files:

bash

$sudo usermod -a -G adm otelcol-contrib
$sudo chmod 644 /var/log/nginx/access.log
$sudo chmod 644 /var/log/nginx/error.log

Restart the collector to apply the changes:
bash
```
$sudo systemctl restart otelcol-contrib
```

Start monitoring

Now that everything is configured, start the OpenTelemetry Collector and verify that data is flowing to New Relic.

Apply the configuration changes:

bash

$sudo systemctl daemon-reload
$sudo systemctl restart otelcol-contrib.service

Verify the service is running:
bash
```
$sudo systemctl status otelcol-contrib.service
```
Expected output: Active: active (running) with no recent errors

Check startup logs:

bash

$sudo journalctl -u otelcol-contrib.service -n 20

Generate test traffic (to create metrics):

bash

$# Make a few requests to your NGINX Plus server
$curl http://localhost

Allow time for initial data to appear in New Relic, then access your NGINX dashboard to verify data collection.

Find and use data

Go to one.newrelic.com > Integrations & Agents.
Select Dashboards, and click NGINX OTel overview dashboard.
In the popup window, select your account.
Click View dashboard, and see your NGINX Plus data in New Relic.

The NGINX Plus metrics are attached to the Metric event type. You can query this data for troubleshooting purposes or to create custom charts and dashboards.

Metrics collected

The OpenTelemetry Collector scrapes metrics from the NGINX Prometheus exporter, which exposes NGINX Plus HTTP API metrics in Prometheus format.

Below are the available NGINX Plus metrics:

Metric	Description	Type
`nginxplus_connections_accepted`	Accepted client connections	Sum
`nginxplus_connections_active`	Active client connections	Gauge
`nginxplus_connections_dropped`	Dropped client connections	Sum
`nginxplus_connections_idle`	Idle client connections	Gauge

Metric	Description	Type
`nginxplus_http_requests_total`	Total http requests	Sum
`nginxplus_http_requests_current`	Current http requests	Gauge

Metric	Description	Type
`nginxplus_ssl_handshakes`	Successful SSL handshakes	Sum
`nginxplus_ssl_handshakes_failed`	Failed SSL handshakes	Sum
`nginxplus_ssl_session_reuses`	Session reuses during SSL handshake	Sum

중요

Note: These metrics are disabled by default. To enable them, see (Optional) Enable additional metrics for NRDOT collector or (Optional) Enable additional metrics for OpenTelemetry Collector Contrib.

Metric	Description	Type
`nginxplus_server_zone_processing`	Client requests that are currently being processed	Gauge
`nginxplus_server_zone_requests`	Total client requests	Sum
`nginxplus_server_zone_responses`	Total responses sent to clients	Sum
`nginxplus_server_zone_responses_codes`	Total responses sent to clients by code	Sum
`nginxplus_server_zone_discarded`	Requests completed without sending a response	Sum
`nginxplus_server_zone_received`	Bytes received from clients	Sum
`nginxplus_server_zone_sent`	Bytes sent to clients	Sum
`nginxplus_server_ssl_handshakes`	Successful SSL handshakes	Sum
`nginxplus_server_ssl_handshakes_failed`	Failed SSL handshakes	Sum
`nginxplus_server_ssl_session_reuses`	Session reuses during SSL handshake	Sum

중요

Metric	Description	Type
`nginxplus_location_zone_requests`	Total client requests	Sum
`nginxplus_location_zone_responses`	Total responses sent to clients	Sum
`nginxplus_location_zone_responses_codes`	Total responses sent to clients by code	Sum
`nginxplus_location_zone_discarded`	Requests completed without sending a response	Sum
`nginxplus_location_zone_received`	Bytes received from clients	Sum
`nginxplus_location_zone_sent`	Bytes sent to clients	Sum

중요

Metric	Description	Type
`nginxplus_cache_size`	Total size of the cache	Gauge
`nginxplus_cache_max_size`	Maximum size of the cache	Gauge
`nginxplus_cache_cold`	Is the cache considered cold	Gauge
`nginxplus_cache_hit_responses`	Total number of cache hits	Sum
`nginxplus_cache_hit_bytes`	Total number of bytes returned from cache hits	Sum
`nginxplus_cache_stale_responses`	Total number of stale cache hits	Sum
`nginxplus_cache_stale_bytes`	Total number of bytes returned from stale cache hits	Sum
`nginxplus_cache_updating_responses`	Total number of cache hits while cache is updating	Sum
`nginxplus_cache_updating_bytes`	Total number of bytes returned from cache while cache is updating	Sum
`nginxplus_cache_revalidated_responses`	Total number of cache revalidations	Sum
`nginxplus_cache_revalidated_bytes`	Total number of bytes returned from cache revalidations	Sum
`nginxplus_cache_miss_responses`	Total number of cache misses	Sum
`nginxplus_cache_miss_bytes`	Total number of bytes returned from cache misses	Sum
`nginxplus_cache_expired_responses`	Total number of cache hits with expired TTL	Sum
`nginxplus_cache_expired_bytes`	Total number of bytes returned from cache hits with expired TTL	Sum
`nginxplus_cache_expired_responses_written`	Total number of cache hits with expired TTL written to cache	Sum
`nginxplus_cache_expired_bytes_written`	Total number of bytes written to cache from cache hits with expired TTL	Sum
`nginxplus_cache_bypass_responses`	Total number of cache bypasses	Sum
`nginxplus_cache_bypass_bytes`	Total number of bytes returned from cache bypasses	Sum
`nginxplus_cache_bypass_responses_written`	Total number of cache bypasses written to cache	Sum
`nginxplus_cache_bypass_bytes_written`	Total number of bytes written to cache from cache bypasses	Sum

Attribute	Description	Example Values
`server_zone`	The name of the server zone (applies to HTTP Server Zones metrics)	`example.com`, `api.example.com`
`code`	HTTP response status code (applies to response metrics)	`1xx`, `2xx`, `3xx`, `4xx`, `5xx`, `200`, `404`, `500`
`location_zone`	The name of the location zone	`/api`, `/images`, `/static`
`cache`	The name of the cache	`my_cache`, `static_cache`
`nginx.server.endpoint`	The NGINX Plus API endpoint URL	`http://localhost:8080/api`
`nginx.deployment.name`	A unique name to identify this NGINX Plus deployment	`production-web-01`, `staging-api`
`nginx.display.name`	A display-friendly name combining "server" prefix with deployment name	`server:production-web-01`
`host.name`	The hostname of the system where NGINX Plus is running	`web-server-01.example.com`
`host.id`	The unique identifier of the host system	`i-1234567890abcdef0`
`logtype`	The type of log being collected (applicable to logs only). Used by New Relic's built-in parsing rules. This attribute is only available when log forwarding is enabled.	`nginx` (for access logs), `nginx-error` (for error logs)

Next steps

Learn more about your data:

Find and query your NGINX data - Access dashboards, create custom queries, and set up alerts
Introduction to NRQL - Learn New Relic's query language for advanced data analysis
Create NRQL alert conditions - Set up custom alerts based on your NGINX Plus metrics

Explore related monitoring:

Monitor self-hosted NGINX with OpenTelemetry - For standard NGINX deployments
Monitor NGINX on Kubernetes with OpenTelemetry - For containerized environments

Monitor self-hosted NGINX Plus with OpenTelemetry

Before you begin .css-21sua1{background:none;border:none;width:0;padding:0;}

Set up NGINX Plus monitoring

팁

Configure the NRDOT collector

Step 2: (Optional) Enable additional metrics

Configure environment and update config path

중요

(Optional) Forward NGINX logs

Step 1: Configure NGINX Plus log format

Step 2: Configure the NRDOT collector for log forwarding

Start monitoring

Step 1: Start the collector

Step 2: Verify data collection

팁

Configure the OpenTelemetry Collector

Step 1: Configure collector configuration

Step 2: (Optional) Enable additional metrics

Set up authentication

(Optional) Forward NGINX logs

Step 1: Configure NGINX Plus log format

Step 2: Configure the OpenTelemetry Collector for log forwarding

Start monitoring

Step 1: Start the collector

Step 2: Verify data collection

Find and use data

Metrics collected

Connections

HTTP

SSL

HTTP Server Zones

Location Zones

Cache

Attributes

Next steps

Before you begin