Find and query your HAProxy data in New Relic

After you've set up HAProxy monitoring with OpenTelemetry, your data appears in New Relic within a few minutes. This page shows you how to find your HAProxy entities, explore metrics, and write NRQL queries.

Find your HAProxy data

Go to one.newrelic.com > All capabilities > Query your data.
Run a query to find your HAProxy data:
```
FROM Metric SELECT uniques(metricName)
WHERE metricName LIKE 'haproxy.%'
SINCE 1 hour ago
```

Query your data with NRQL

Use these example NRQL queries to analyze your HAProxy data:

-- Sessions per second across frontends
FROM Metric SELECT average(haproxy.sessions.rate)
WHERE haproxy.service_name = 'FRONTEND'
FACET haproxy.proxy_name
TIMESERIES

-- Error rates by backend
FROM Metric SELECT rate(sum(haproxy.responses.errors), 1 minute) AS 'Errors/min'
WHERE haproxy.service_name = 'BACKEND'
FACET haproxy.proxy_name
TIMESERIES

-- Bytes throughput (in + out)
FROM Metric SELECT rate(sum(haproxy.bytes.input), 1 minute) AS 'Bytes In/min',
  rate(sum(haproxy.bytes.output), 1 minute) AS 'Bytes Out/min'
FACET haproxy.proxy_name
TIMESERIES

-- Backend server health
FROM Metric SELECT latest(haproxy.active) AS 'Active Servers',
  latest(haproxy.backup) AS 'Backup Servers'
WHERE haproxy.service_name = 'BACKEND'
FACET haproxy.proxy_name

-- Request queue depth (indicates backend saturation)
FROM Metric SELECT max(haproxy.requests.queued)
WHERE haproxy.service_name = 'BACKEND'
FACET haproxy.proxy_name
TIMESERIES

Troubleshoot data visibility

Allow a few minutes for initial data ingestion.
Check the time range — ensure you're looking at recent data (last 30 minutes).

Query for any HAProxy metrics:

FROM Metric SELECT count(*) WHERE metricName LIKE 'haproxy.%' SINCE 30 minutes ago

Verify the collector is running:
bash
```
$# Self-hosted
$sudo systemctl status otelcol-contrib
$# or
$sudo systemctl status nrdot-collector
$
$# Kubernetes
$kubectl get pods -n newrelic
$kubectl logs -n newrelic -l app.kubernetes.io/name=nr-k8s-otel-collector
```
Check that the HAProxy stats endpoint is accessible from the collector.

Check collector logs for errors:

bash

$# Self-hosted
$sudo journalctl -u otelcol-contrib -n 50 --no-pager
$
$# Kubernetes
$kubectl logs -n newrelic deploy/nr-k8s-otel-collector-deployment --tail=50

Verify HAProxy stats endpoint is consistently accessible.
Check for network connectivity issues between the collector and New Relic's OTLP endpoint.
Ensure HAProxy isn't rate-limiting stats endpoint requests.

Next steps

HAProxy OTel metrics reference — complete metrics reference with descriptions
Introduction to NRQL — learn New Relic's query language for advanced analysis
Create NRQL alert conditions — set up alerts based on your HAProxy metrics
Monitor self-hosted HAProxy — setup for Linux VMs or bare metal
Monitor HAProxy on Kubernetes — automatic pod discovery for containerized environments

Find and query your HAProxy data in New Relic

Find your HAProxy data

Use the entity explorer

Use Integrations & Agents

Use the query builder

Query your data with NRQL

Troubleshoot data visibility

No data appears in New Relic

Data appears intermittent

Next steps

Find and query your HAProxy data in New Relic

Find your HAProxy data .css-21sua1{background:none;border:none;width:0;padding:0;}

Use Integrations & Agents

Use the query builder

Query your data with NRQL

Troubleshoot data visibility

No data appears in New Relic

Data appears intermittent

Next steps

Find your HAProxy data