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 nri-prometheus integration, our Redpanda dashboard takes advantage of nri-prometheus 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.
Before getting Redpanda data into New Relic, you'll need to install our infrastructure agent, then expose your metrics by configuring nri-prometheus.
- Follow our guided install to instrument your system with the infrastructure agent. You can install the infrastructure agent via the command line using our docs.
- Create a file named
- Add the following configuration to your
nri-prometheus-config.ymlfile to scrape for RedPanda data. Your configuration file should match our snippet in the nri-prometheus repository:
integrations:- name: nri-prometheusconfig:# When standalone is set to false, nri-prometheus requires an infrastructure agent to work and send data. Defaults to truestandalone: false# If using the infrastructure agent, emitters have to include infra-sdkemitters: infra-sdk# The name of your cluster. The name of your cluster must be consistent across New Relic products so the infrastructure agent and nri-prometheus can scrape data from the cluster.cluster_name: "YOUR_EXPORTER_NAME"targets:- description: Redpanda metrics are captured in the below urlsurls: ["http://localhost:9644/metrics", "http://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, use with care.audit: false# The HTTP client timeout when fetching data from endpoints. Defaults to "5s" if it's not set.# scrape_timeout: "5s"# Length in time to distribute the scraping from the endpoints. Default to "30s" if it's not set.scrape_duration: "5s"# Number of worker threads used for scraping targets.# For large clusters with many (>400) endpoints, 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: falsetimeout: 10s
Once you've installed the Redpanda quickstart, you can see your critical Redpanda data in New Relic. To confirm that your data is reporting:
- Go to one.newrelic.com, then click Metrics & events.
- Run the following NRQL query:
FROM Metric SELECT latest(vectorized_application_uptime).
- Once you've confirmed that New Relic ingested your Redpanda metrics, go to Dashboards from one.newrelic.com to see your RedPanda dashboard.
If you want to further customize your RedPanda dashboards, you can learn more about building NRQL queries and managing your in the New Relic UI: