• Log inStart now

Redpanda integration

With our Redpanda dashboard, you can track your cluster-level metrics, Redpanda scheduling groups, and your service errors and uptime. Built with our infrastructure agent and our Prometheus OpenMetrics integration, our Redpanda dashboard take advantage of OpenMetrics endpoint scraping, so you can view all your most important data, all in one place.

After setting up Redpanda with New Relic, your data will display in dashboards like these, right out of the box.

Install the infrastructure agent and Prometheus OpenMetrics integration

Before getting Redpanda data into New Relic, you'll need to install our infrastructure agent, then expose your metrics by installing Prometheus OpenMetrics.

Configure Prometheus OpenMetrics for RedPanda

After you've installed Prometheus OpenMetrics, you need to configure the nri-prometheus-config.yml file to scrape for RedPanda data. Your configuration file should match our snippet in the nri-prometheus repository:

- name: nri-prometheus
# When standalone is set to false, the infrastructure agent will need to send data so nri-prometheus can work. Defaults to true.
standalone: false
# If using the infrastructure agent, emitters must be set to infra-sdk
emitters: infra-sdk
# The name of your cluster. The name of your cluster must be consistent across New Relic products so the infrastructure agent and Prometheus OpenMetrics can scrape data from the cluster.
cluster_name: "YOUR_EXPORTER_NAME"
- description: "Redpanda metrics are captured in the below urls"
urls: ["'localhost:9644/metrics', 'localhost:9644/public_metrics']
# tls_config:
# ca_file_path: "/etc/etcd/etcd-client-ca.crt"
# cert_file_path: "/etc/etcd/etcd-client.crt"
# key_file_path: "/etc/etcd/etcd-client.key"
# Specifies whether or not the integration should run in verbose mode. Defaults to false.
verbose: false
# Specifies whether or not the integration should run in audit mode. Defaults to false.
# Audit mode logs the uncompressed data sent to New Relic. Use this to log all data sent.
# It does not include verbose mode. This can lead to a high log volume, so use with care.
audit: false
# The HTTP client timeout when fetching data from endpoints. Defaults to 30s.
# scrape_timeout: "30s"
# Length in time to distribute the scraping from the endpoints.
scrape_duration: "5s"
# Number of worker threads used for scraping targets.
# For large clusters with more than 400 endpoints, we recommend that you slowly increase until scrape time falls between the desired `scrape_duration`.
# Increasing this value too much will result in huge memory consumption if too many metrics are being scraped.
# Default: 4
# worker_threads: 4
# Specifies whether or not the integration should skip TLS verification. Defaults to false.
insecure_skip_verify: false
timeout: 10s

Get RedPanda metrics as a dashboard

Once you've installed the Redpanda quickstart, you can see your critical Redpanda data in New Relic. To confirm that your data is reporting:

  1. Go to one.newrelic.com, then click Metrics & events.
  2. Run the following NRQL query: FROM Metric SELECT latest(vectorized_application_uptime).
  3. Once you've confirmed that New Relic ingested your Redpanda metrics, go to Dashboards from one.newrelic.com to see your RedPanda dashboard.

What's next?

If you want to further customize your RedPanda dashboards, you can learn more about building NRQL queries and managing your dashboards in the New Relic UI:

Copyright © 2023 New Relic Inc.

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