To get up and running with Auto-telemetry with Pixie, you start with our guided installation. The guided installation deploys Pixie with New Relic's Kubernetes integration on your cluster. You don't need to do any further configuration or installation to start using Pixie.
If you want to install Auto-telemetry with Pixie on multiple clusters, re-run the guided install for each additional cluster.
- You must be a New Relic full platform user. Other user-related requirements:
- Review this Pixie data security overview for actions to take to secure your data.
- Make sure you have sufficient memory: Pixie requires 2Gb of memory per node in your cluster.
- Review the other Pixie technical requirements.
Use the following table to find out where to start installing Auto-telemetry with Pixie. Where you start the installation depends on whether you already have a New Relic or Pixie account, or both.
Start the guided install at the beginning of the process.
If you already have both types of accounts, and used the same email address for each of them, click the New Relic icon in the Pixie UI. This brings you to the Configure the HELM command/manifest (yaml) file section of the guided installation. Then, follow the steps.
If you're using different email addresses in Pixie and New Relic, create a new account for either Pixie or New Relic to match email addresses across both products. You can also contact New Relic support to manually link your existing New Relic account with your Pixie account.
If you follow a link to New Relic from the Pixie UI and do not have a New Relic account, you must first create one. Click the New Relic icon in the Pixie UI, and follow the steps to create a New Relic account. When you do so, your Pixie account is linked to it. Then, continue the guided install process with these steps.
- Open our New Relic One guided install.
- Select the account you want to use for the guided install, and click Continue. Note: if you have a single account, you won't see this option.
- Select Kubernetes and then continue with step one in the next section.
If you arrived in the guided installation process by following a link from Pixie or from within New Relic, your steps begin here.
Select the account and cluster for the install. If needed, select a namespace.
Currently, Pixie performs best on clusters with up to 100 nodes (exceeding 100 nodes can lead to excessive memory usage and scripts failing to run). Friendly reminder: autoscaling can quickly drive up your node numbers.
Select the data you want to gather, observe, and debug, and click Continue.
On the Choose install method page, select either Helm or manifest.
Click Continue to open the Listening for data page.
When you get the message, See your data, click Kubernetes Cluster Explorer to see your cluster.
Auto-telemetry with Pixie might restart after installation. This is caused by the auto update feature.
Contact support to unlink a Pixie account from your New Relic account. Be aware that if you unlink a Pixie account that was created automatically through the guided install, you'll lose access to that Pixie account.
If you want to reduce the amount of Pixie data that New Relic ingests, you can add the following parameters to your Helm chart during installation. Note that the data still exists in Pixie:
excludeNamespacesRegex- use to identify the namespaces that you want to exclude from sending observability data to New Relic. If empty, data for all namespaces is sent to New Relic. Example:
excludePodsRegex- use to identify pods across all namespaces that you want to exclude from sending observability data to New Relic. If empty, data for all pods (except those in excluded namespaces) is sent to New Relic. Example:
Learn more about the available parameters for the
newrelic-pixieHelm chart here.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.