New Relic is a performance tracking and analytics tool that helps engineers gain visibility into their software. Integrating New Relic with Cortex allows you to:
Discover entities and track ownership
View SLO and monitoring information on entity pages in Cortex
Embed New Relic dashboards on entity pages in Cortex
Create Scorecards to drive alignment on projects involving New Relic metrics
Before getting started:
As a full platform user in New Relic, create a .
New Relic user keys are linked to the account they were created from, so if this account is ever deleted, the integration with Cortex will stop working.
In Cortex, navigate to the :
Click Integrations from the main nav. Search for and select New Relic.
Click Add configuration.
Configure the New Relic integration form:
Once you save your configuration, you'll see it listed on the integration's settings page in Cortex. If you’ve set everything up correctly, you’ll see the option to Remove Integration in Settings.
You can also use the Test all configurations button to confirm that the configuration was successful. If your configuration is valid, you’ll see a banner that says “Configuration is valid. If you see issues, please see documentation or reach out to Cortex support.”
After setting up the integration, you will be redirected to the where you can enable the cross-account access feature. If you have an account that supports subordinate accounts, you can enable this setting to fetch applications and SLOs for all the accounts that are under the configured one.
The New Relic integration has multi-account support. You can add a configuration for each additional by repeating the process above.
Each configuration requires an alias, which Cortex uses to correlate the designated with registrations for various entities. Registrations can also use a default configuration without a listed alias. You can edit aliases and default configurations from the New Relic page in your Cortex settings. Select the edit icon next to a given configuration and toggle Set as default on. If you only have one configuration, it will automatically be set as the default.
There are two ways to auto-map New Relic applications and services to Cortex entities:
By default, Cortex will use the (e.g. my-entity) or its name as the "best guess" for New Relic applications. For example, if your Cortex tag is my-entity, then the corresponding application in New Relic should also be my-entity. The name is not case-sensitive.
If your New Relic applications don’t cleanly match the Cortex tag or name, you can override this in the Cortex entity descriptor.
Cortex also supports mapping New Relic applications to Cortex entities via New Relic tagKeys. By default, a Cortex entity will be mapped to a New Relic application or service with New Relic tag key = "service" and tag value = the service's Cortex tag.
Note: Cortex does not support auto-mapping of SLOs. SLOs have to be defined via the entity YAML or attached to a mapped application or service.
Dependencies
Cortex automatically maps dependencies between your entities by utilizing New Relic's data.
Say you have two applications in NewRelic (Application A and Application B), and in the service map Application A calls Application B. In Cortex you have two Entities (Cortex Entity A and Cortex Entity B), where Cortex Entity A is mapped to New Relic Application A and Cortex Entity B is mapped to New Relic Application B. Cortex will take the mapped relationship from Application A to Application B and create a dependency from Cortex Entity A to Cortex Entity B.
See the for instructions on importing entities.
APM services
New Relic application metrics can be fetched for each entity using application IDs or tags.
Instructions to find your Application ID can be found in the . You can also find the Application ID in the URL in New Relic.
You can also find information on finding and managing tags in the .
OpenTelemetry
services can be associated with the entity only using tags. For this type of service New Relic doesn't generate application ID.
Cortex fetches OpenTelemetry data every 5 minutes, but the data refresh may take longer depending on how much data you have.
Embeds
Cortex can also embed dashboards from New Relic.
Learn more about embedding charts in the page.
SLOs
SLO can be fetched for each entity using New Relic entity GUID for respective SLO or associated service. Detailed instructions how to obtain entity GUID can be found in .
Fetched SLO information can be found in the Operations and Integrations sections of an entity page.
If the alias is not specified, like with the third ID above, Cortex will use the default configuration.
If you use the GUID for a parent service to define the SLOs for a given entity, Cortex will import all SLOs associated with that service.
When entities are tied to New Relic, SLO and monitoring information appear under the Monitoring section on the overview of the .
More data is available under the Monitoring page in the entity's sidebar:
Throughput
Response time
Error rate
Apdex target
In the SLOs section, you'll be able to see a list of all SLOs tied to that entity, the target and current SLO score, and the period of time the SLO is being calculated for. For example, if the time listed is "7 days ago," then the SLO is looking at the time range starting 7 days ago to now..
The SLO name will display in green when passing and orange when failing.
If you've defined in an entity's YAML, you'll be able to view the graphs from an entity's details page. Open the Dashboard page in the entity's sidebar. All dashboards defined in the descriptor will be embedded on this page.
New Relic dashboards must be defined individually for each entity.
detected from New Relic will appear in . You can in the Relationship Graph.
With the New Relic integration, you can create Scorecard rules and write CQL queries based on New Relic performance metrics.
See more examples in the in Cortex.
OpenTelemetry metrics
OpenTelemetry metrics available in the can be accessed or manipulated for a given entity by combining CQL and native query.
The following options are available to get assistance from the Cortex Customer Engineering team:
Email: , or open a support ticket in the in app Resource Center
Slack: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a :ticket: reaction to a question in Slack, and the team will respond directly.
Don’t have a Slack channel? Talk with your Customer Success Manager.
Account alias: Enter a name for this account.
Personal key: Enter the user key you generated in New Relic.
Account ID: Enter the ID for the account that the user key was generated with.
Use EU region: Optionally enable this toggle to use the EU region of New Relic.
Click Save.
You can customize the tag key names on the New Relic settings page in Cortex.
Host count
Instance count
Concurrent instance count
Concurrent stance count
Error rate
GUID
Host count
ID
Instance count
Name
Response time
Throughput
Type
If there is not an application ID set in the entity descriptor, a Scorecard rule based on this expression will fail.
Definition: newrelic.applications()
Example
You can use this expression in a Scorecard rule to make sure entities' Apdex score is at least 0.9:
Name
Operation
Remaining budget
SLI value
SLO target
Source
Thresholds
SLO datum (timeseries data for the SLI)
Datum
Ts
Named threshold (SLOs thresholds like "warning" or "error" states)
Name
Threshold
Definition: slos
Examples
You can use SLO data from New Relic to evaluate entities in Scorecards. For an onboarding Scorecard, you can make sure that entities have at least 1 SLO defined:
For a project standards Scorecard, you can also use this expression to make sure entities are passing all of their SLOs:
applications
Specifies that the APM service should be found by application ID
✓
applicationID
ID for the application that the service belongs to
✓
alias
Alias for the configuration in Cortex (only needed if you have opted into multi-account support)
tags
Specifies that the APM service should be found by tag
✓
tag
Tag key for the APM service(s)
✓
value
Tag value for the APM service(s)
✓
alias
Alias for the configuration in Cortex (only needed if you have opted into multi-account support)
tags
Specifies that the OpenTelemetry service should be found by tag
✓
tag
Tag key for the APM service(s)
✓
value
Tag value for the APM service(s)
✓
alias
Alias for the configuration in Cortex (only needed if you have opted into multi-account support)
type
Specifies the source of the embed; in this case, should be newrelic
✓
url
URL for the dashboard. It must be publicly accessible, or if you can access the iFrame via VPN, it should be accessible in Cortex while also on the VPN.
✓
id
New Relic entity guid for the SLO or the associated service; if you use the GUID for a parent service, all SLOs associated with it will be imported into Cortex
true
alias
Alias for the configuration in Cortex (only needed if you have opted into multi-account support)
x-cortex-apm:
newrelic:
applications:
- applicationId: 1234567
alias: Default-App
- applicationId: 8904321
alias: Another-Appx-cortex-apm:
newrelic:
tags:
- tag: tagKey
value: tagValue
alias: Default-Appx-cortex-apm:
newrelic:
tags:
- tag: tagKey
value: tagValue
alias: Default-Appx-cortex-dashboards:
embeds:
- type: newrelic
url: https://chart-embed.service.newrelic.com/example/1a234bc5-d6e7-890f-g123-456h7ij8901 x-cortex-slos:
newrelic:
- id: MjU5ODYxOXxFWFR8U0VSVklDRV9MRVZFTHiw0TI5ODQ
alias: my-default-alias
- id: MjU5ODYxOXxFWFR8U0VSVklDRV9MRVZFTHiw0TI76QB
alias: my-other-alias
- id: MjU5ODYxOXxFWFRAB6VSVklDRV9MRVZFTHiw0TI76QDnewrelic != nulljq(newrelic.rawNrql("SELECT percentile(duration) FROM PageView WHERE = '" + newrelic.applications().firstOrNull().name + "' SINCE 3 weeks ago COMPARE WITH 1 week AGO TIMESERIES AUTO"), "[.[].\"percentile.duration\".\"95\"] | add / length") < 500newrelic.rawNrql("SELECT average(`http.server.requests`) FROM Metric WHERE `entity.guid` = '"+newrelic.applications().getOrNull(0)?.guid+"' SINCE 7 DAYS AGO")newrelic.applications().all(application) => application.apdexScore >= 0.9newrelic.rawNrql("SELECT latest(`process.cpu.usage`) FROM Metric WHERE `entity.guid` = '"+newrelic.applications().getOrNull(0)?.guid+"' SINCE 30 MINUTES AGO TIMESERIES")slos().length > 0slos().all((slo) => slo.passing) == trueOn the integration settings page, click the Logs tab to view logs from the last 7 days. Learn more in Troubleshooting with integration logs.