Find and query your NGINX data in New Relic

View your NGINX data in New Relic

Once your setup is complete and data is flowing, you can view your NGINX metrics and logs in New Relic and create custom alerts.

Go to one.newrelic.com > Integrations & Agents
Click Dashboards
Search and click NGINX (OpenTelemetry Collector) dashboard
A Dashboard setup page opens. If you have already set up the data source, click Skip this step. Otherwise, click See installation docs and follow the instructions to set up your data source. After completing setup, return to the dashboard setup page and click Skip this step.
Click View dashboard.

Query your data with NRQL

You can create custom queries to analyze your NGINX data:

Example queries:

-- View request rate over time
FROM Metric SELECT rate(sum(nginx.requests), 1 minute)
WHERE nginx.deployment.name = 'production-web-01'
TIMESERIES

-- Check connection states
FROM Metric SELECT latest(nginx.connections_current)
WHERE nginx.deployment.name = 'production-web-01'
FACET state

-- Analyze log patterns (if log forwarding enabled)
FROM Log SELECT count(*)
WHERE nginx.deployment.name = 'production-web-01'
FACET status SINCE 1 hour ago

Query trace data with NRQL

If you've enabled distributed tracing with ngx_otel_module, you can also query trace and span data:

-- NGINX spans by name
FROM Span SELECT count(*)
WHERE nginx.deployment.name = 'production-web-01'
FACET name
SINCE 1 hour ago

-- Distributed traces flowing through NGINX
-- Shows all services participating in traces that include NGINX
FROM Span SELECT uniques(service.name)
WHERE trace.id IN (
  SELECT uniques(trace.id) FROM Span
  WHERE nginx.deployment.name = 'production-web-01'
  SINCE 30 minutes ago LIMIT 10
)
SINCE 30 minutes ago

-- Service relationships involving NGINX
FROM Relationship SELECT *
WHERE source.entityName = 'server:production-web-01'
  OR target.entityName = 'server:production-web-01'
SINCE 1 day ago

Replace production-web-01 with your nginx.deployment.name. The NGINX entity name defaults to server:<nginx.deployment.name> (set by the nginx.display.name transform in your collector config).

Troubleshoot data visibility

Allow some time - Initial data ingestion can take a few minutes
Check the time range - Ensure you're looking at recent data
Verify deployment name - Use the exact name from your Collector config

Check for data with NRQL:

FROM Metric SELECT * WHERE nginx.deployment.name LIKE '%production%' LIMIT 1

Check Collector logs for errors:
bash
```
$sudo journalctl -u otelcol-contrib -n 50
```
Verify NGINX is generating traffic - Test with curl http://localhost
Check authentication - Ensure license key and endpoint are correct

Next steps

Learn more about your data:

NGINX distributed tracing - Enable ngx_otel_module for distributed tracing and service relationships
NGINX OpenTelemetry metrics and attributes reference - Complete metrics reference with descriptions and examples
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 metrics

Setup guides:

Monitor self-hosted NGINX with OpenTelemetry - Complete setup for on-host deployments
Monitor NGINX on Kubernetes with OpenTelemetry - Complete setup for Kubernetes deployments

Find and query your NGINX data in New Relic

View your NGINX data in New Relic

Through Integrations & Agents

Through Infrastructure monitoring

Query your data with NRQL

Query trace data with NRQL

Troubleshoot data visibility

If you don't see data

If data appears intermittent

Next steps

Find and query your NGINX data in New Relic

View your NGINX data in New Relic .css-21sua1{background:none;border:none;width:0;padding:0;}

Through Infrastructure monitoring

Query your data with NRQL

Query trace data with NRQL

Troubleshoot data visibility

If you don't see data

If data appears intermittent

Next steps

View your NGINX data in New Relic