New Relic

Qovery creates it as a Helm release on the environment’s own cluster, as a Blueprint service in one of your environments.


Catalog name	`helm-newrelic`
Category	Observability
Provider	HELM
Engine	helm
Major versions (latest release)	`default` (1.0.4)
Source	HELM/newrelic/default

New to this? You don’t need to know Kubernetes or Helm. Qovery installs New Relic on your cluster with Helm and runs it for you: you fill in a form, or paste the prompt below into your coding agent. Qovery tells you when a newer version of the Blueprint is available. Check the requirements in the Reference section before you start, and try it first in a development environment.

Create it

Console
CLI and API
Coding agent

Open the environment, then New service › Blueprint.
Find New Relic in the catalog and pick the major version.
Fill in the variables. Required ones are marked; the others use their defaults.
Create the service, and deploy it now or later.

List the catalog to get the latest tag, then create the service from it. qovery api signs the requests with your CLI session.

ORG_ID="REPLACE_WITH_ORGANIZATION_ID"
ENV_ID="REPLACE_WITH_ENVIRONMENT_ID"

qovery api "organization/$ORG_ID/blueprint/catalog" | jq '.. | objects | select(.name? == "helm-newrelic")'

cat > blueprint.json <<'EOF'
{
  "name": "helm-newrelic",
  "tag": "HELM/newrelic/default/1.0.4",
  "icon": "app://qovery-console/newrelic",
  "variables": [
    {
      "name": "newrelic_license_key",
      "value": "REPLACE_WITH_NEWRELIC_LICENSE_KEY",
      "is_secret": true
    },
    {
      "name": "cluster_name",
      "value": "REPLACE_WITH_CLUSTER_NAME"
    }
  ]
}
EOF
BLUEPRINT_ID=$(qovery api "environment/$ENV_ID/blueprint" --method POST --input - < blueprint.json | jq -r .id)
rm blueprint.json   # it can hold secret values
qovery api "blueprint/$BLUEPRINT_ID/deploy" --method POST
qovery api "blueprint/$BLUEPRINT_ID"   # status of the latest deployment

Replace each REPLACE_WITH_ value. Add optional variables to variables the same way.

Paste this into Claude Code, Cursor, Codex or another coding agent with the Qovery agent skills installed (curl -fsSL https://skill.qovery.com/install.sh | bash).

Prompt

Add the Qovery Blueprint New Relic (helm-newrelic) to one of my Qovery environments and deploy it. Ask me for newrelic_license_key and cluster_name.
Ask me before deploying to a production environment.
Docs: https://www.qovery.com/docs/configuration/blueprints/helm-newrelic.md

You don’t add any file to your repository. Qovery creates the Blueprint from the Console or the API.

Variables and outputs

Generated from qbm.yml at HELM/newrelic/default/1.0.4, the manifest the Console form is built from.

All 6 variables

Name	Type	Required	Default	Secret	Description
`newrelic_license_key`	string	Yes		Yes	New Relic ingest license key
`cluster_name`	string	Yes			Reported to New Relic. Letters, digits, hyphens, underscores; max 64 chars.
`low_data_mode`	string		`true`		Reduce data ingest (drops some high-cardinality data) to control cost
`enable_kube_events`	string		`true`		Collect Kubernetes events (nri-kube-events)
`enable_logging`	string		`false`		Deploy the New Relic logging DaemonSet (Fluent Bit) to ship pod logs
`ksm_memory`	string		`128Mi`		Request and limit of kube-state-metrics, as a Kubernetes quantity

Reference

From the Blueprint’s README. Deploys New Relic Kubernetes monitoring via the official newrelic/nri-bundle Helm chart (8.0.18): the infrastructure agent (per-node DaemonSet), kube-state-metrics, metadata injection, Kubernetes events, and optional pod-log shipping.

Credentials

A New Relic ingest license key supplied as the sensitive newrelic_license_key variable, plus a cluster_name reported to New Relic. Data appears in your New Relic account (no in-cluster endpoint to connect to).

Variables

Name	Type	Sensitive	Default	Description
`newrelic_license_key`	string	yes	—	New Relic ingest license key (required)
`cluster_name`	string		—	Cluster name reported to New Relic (required)
`low_data_mode`	string		`true`	Reduce ingest to control cost (`true`/`false`)
`enable_kube_events`	string		`true`	Collect Kubernetes events (`true`/`false`)
`enable_logging`	string		`false`	Deploy the Fluent Bit log DaemonSet (`true`/`false`)
`ksm_memory`	string		`128Mi`	Memory request/limit for kube-state-metrics

Notes

Deploys cluster-wide resources (DaemonSets, ClusterRole/Binding across sub-charts) — allowClusterWideResources: true.
Resources: kube-state-metrics is set explicitly (the bundle leaves it unbounded by default); the New Relic agent sub-charts (newrelic-infrastructure, logging) use New Relic’s own tuned resource defaults. Override per sub-chart if you need tighter limits.
low_data_mode defaults to true to keep ingest (and cost) down; set false for full-fidelity data.
Chart pinned to nri-bundle 8.0.18. This is the official New Relic chart (not Bitnami).
The nri-bundle meta-chart has no single appVersion, so this blueprint lives under default per the catalog’s versioning convention.

Overview

Account & Organization

Clusters & Cloud

Source Control

Projects & Environments

Services

Deployment & CI/CD

Environment Variables & Secrets

Observability

Notifications

Networking & Advanced

Create it

Variables and outputs

Reference

Credentials

Variables

Notes

​Create it

​Variables and outputs

​Reference

​Credentials

​Variables

​Notes

Create it

Variables and outputs

Reference

Credentials

Variables

Notes