> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/platform-administration/settings/data-streaming/data-streaming-new-relic.md). # How to use Data Streaming with New Relic Learn how to automatically stream logs and execution data from the Digibee Integration Platform to New Relic using an Ingest License Key. ## **How Data Streaming works with New Relic** Data Streaming sends logs and execution data from the Digibee Integration Platform to New Relic automatically. Unlike Splunk, which uses a HEC Token, New Relic receives the data through OTLP (OpenTelemetry Protocol), its native ingestion protocol. To authenticate the data, New Relic uses an Ingest License Key, the same key that any OpenTelemetry agent uses to send data to your account. ## **Before you begin** To set up Data Streaming with New Relic, you need: * **The `data-streaming-manager` role:** Only users with this role can create, update, read, and delete data streams. To learn more, read [Roles](/documentation/platform-administration/administration/new-access-control/access-control-roles.md). * **Access to a New Relic account:** The account that will receive the data from the Digibee Integration Platform. ## **Step-by-step guide** {% stepper %} {% step %} ### **Create an Ingest License Key in New Relic** 1. In New Relic, click your account icon in the top-right corner and select **API keys**. 2. Click **Create a key**. 3. In **Type**, select **Ingest - License**. Don't use the **User** or **Browser** types. They have a different format, and this integration doesn't accept them. 4. Give the key a descriptive name, for example `digibee-`, and confirm. 5. Copy the key value from the banner at the top of the screen. A valid Ingest License Key has exactly 40 alphanumeric characters. {% hint style="warning" %} New Relic shows the full key value only once, right after you create the key. After that, the screen shows only a masked version, for example `a2a4113f********`, and you can't display or copy the value again. If you lose the value, you must create a new key. {% endhint %} {% endstep %} {% step %} ### **Configure Data Streaming on the Digibee Integration Platform** 1. On the Digibee Integration Platform, click **Settings** in the top-right corner of the page. 2. In the Settings menu, click **Data streaming**. 3. Click **Create**. 4. In **Vendor**, select **New Relic**. 5. In **Streaming type**, select **Logs**, **Executions**, or both. 6. Fill in the connection details: * **Host:** The OTLP endpoint for your New Relic account region, without `https://`. Use `otlp.nr-data.net` for US accounts or `otlp.eu01.nr-data.net` for EU accounts. * **API Key:** The Ingest License Key you copied in Step 1. 7. Click **Save**. {% hint style="info" %} To identify your New Relic account region, check the address you use to access New Relic: `one.newrelic.com` indicates a US account, and `one.eu.newrelic.com` indicates an EU account. A license key that starts with `eu01xx` also indicates an EU account. {% endhint %} {% endstep %} {% step %} ### View the data in New Relic New Relic automatically creates a service entity for each distinct value of the `service.name` attribute it receives. Unlike Splunk and Datadog, New Relic has no manual filter to separate logs from executions. #### **Find the entities** 1. In New Relic, go to **APM & Services** and select **Services - OpenTelemetry**. You should see one entity for each data type received, for example `pipeline-logs` for logs and `completed-executions` for executions. 2. Click an entity. 3. Open the **Logs** tab to explore the data. {% hint style="info" %} This integration sends only logs and executions, both as OTLP log records. It doesn't send traces, so the **Distributed tracing** tab of each entity stays empty. This doesn't indicate a configuration problem. {% endhint %} #### **Confirm the data with a query** If an entity doesn't appear in the list yet, use NRQL (New Relic Query Language) in the Query Builder to confirm that the data arrived. The following query counts the execution records received in the last hour: {% code overflow="wrap" %} ```sql FROM Log SELECT count(*) WHERE service.name = 'completed-executions' SINCE 1 hour ago ``` {% endcode %} New Relic creates an entity only after the first record with that `service.name` arrives. For executions, at least one pipeline execution must finish in the configured realm before the entity appears. {% endstep %} {% endstepper %} ## **Troubleshooting** Data can take from a few seconds to a few minutes to appear in New Relic after you create the stream. If the stream status on the Digibee Integration Platform shows `down` right after you create it, this is expected. The internal check only considers activity from the last 5 minutes. Run a pipeline execution and wait for the status to update. If no data appears in New Relic after about 10 minutes of activity in the realm, check the `NrIntegrationError` table first. New Relic can accept the data and then reject it asynchronously. The following query lists the ingestion errors from the last hour: ```sql SELECT * FROM NrIntegrationError SINCE 1 hour ago ``` If the cause is still unclear, [contact the Digibee Support team](/documentation/troubleshooting/help-and-faq/support.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digibee.com/documentation/platform-administration/settings/data-streaming/data-streaming-new-relic.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.