• /
  • EnglishEspañolFrançais日本語한국어Português
  • Log inStart now

No data appears in the UI

Problem

You have installed the New Relic eBPF agent, but you don't see any eBPF data in your New Relic UI, or you're missing specific metrics or spans for certain protocols.

Solution

If no eBPF data appears at all:

  1. Check network connectivity: Ensure that the OTLP (OpenTelemetry Protocol) endpoint is not blocked by any firewall or network configuration. Verify these URLs are accessible:
    • otlp.nr-data.net:443
    • otlp.eu01.nr-data.net:443 (EU region only)
    • https://downloads.newrelic.com
    • https://nr-downloads-ohai-staging.s3.amazonaws.com

Important

Ensure ports 4317 and 443 are unblocked at multiple levels:

  • Cluster level: For Kubernetes deployments (e.g., AKS clusters), verify the cluster's network security groups allow outbound traffic on these ports
  • Infrastructure level: Check that security software (e.g., Microsoft Defender, corporate firewalls) isn't blocking these ports at the infrastructure level

Port blocking can occur at both levels simultaneously, causing connectivity issues even if one level is properly configured.

  1. Verify agent installation: Check that the eBPF agent services are running:

    For Linux hosts:

    bash
    $
    sudo systemctl status newrelic-ebpf-agent
    $
    sudo systemctl status newrelic-ebpf-agent-client

    For Kubernetes:

    bash
    $
    kubectl get pods -n newrelic
  2. Check agent logs: Look for errors in the agent logs. Successful installation should show:

    [STEP-7] => Successfully started the eBPF Agent.
  3. Use the correct filter: In the New Relic UI, filter entities by instrumentation.name = nr_ebpf to see eBPF-monitored services.

If specific metrics or spans are missing:

  1. Verify protocol configuration: Check that metrics and spans are enabled for the specific protocol in your configuration file:

    For Linux hosts (/etc/newrelic-ebpf-agent/newrelic-ebpf-agent.conf):

    bash
    $
    PROTOCOLS_HTTP_ENABLED="true"
    $
    PROTOCOLS_HTTP_SPANS_ENABLED="true"
    $
    PROTOCOLS_MYSQL_ENABLED="true"
    $
    # ... other protocols

    For Kubernetes (in your values.yaml):

    protocols:
    http:
    enabled: true
    spans:
    enabled: true
    mysql:
    enabled: true
  2. Restart the agent after configuration changes:

    For Linux hosts:

    bash
    $
    sudo systemctl restart newrelic-ebpf-agent

    For Kubernetes:

    bash
    $
    helm upgrade nr-ebpf-agent newrelic/nr-ebpf-agent -n newrelic --reuse-values
  3. Check data filtering settings: Verify that your entity isn't being excluded by configuration parameters like DROP_DATA_FOR_ENTITY or dropDataServiceNameRegex.

Additional verification steps:

  1. Filter entities by host: Use the host.name tag in the New Relic UI to filter entities running on a specific host.

  2. Check entity naming: Entities are automatically named as follows:

    • Linux hosts: processName:workingDirectory:[port] (e.g., ruby:/path/to/app:[5678])
    • Docker: processName:containerName:[port] (e.g., java:my-container:[8080])
    • Kubernetes: Based on Kubernetes service name (e.g., mysql-database-service)
  3. Verify custom naming: If using NEW_RELIC_APP_NAME, the entity will appear with -ebpf suffix.

Copyright © 2025 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.