New Relic Integration
Ingest production incidents and deployment markers for Quality and DORA metrics.
Why connect New Relic
New Relic is a Monitoring & Observability source. After you connect, the platform reads your account’s alert issues and deployment markers on a schedule and uses them for Quality (incident rates, MTTR) and DORA (deployment frequency) views.
The integration is read-only. We never change alerts, policies, or ingest telemetry into New Relic.
What you need
- A New Relic account with access to Applied Intelligence issues (alerts).
- A User API key (not an ingest or license key).
- Your numeric Account ID (shown in New Relic → your name, lower left → API keys).
Select New Relic in your tech stack under Monitoring & Observability if you use it today.
Setup
- In New Relic, open API keys and create a User key with read access to the account you want to connect.
- In the platform, go to Settings → Integrations (or onboarding Integrations) and choose Connect on New Relic.
- Enter Account ID, User API key, and Data region (US or EU; match where your account lives).
- Click Test connection. A successful test shows your New Relic user name and account name.
- Click Connect (or Save changes) to store encrypted credentials.
Incidents and deployment markers sync on the platform’s batch schedule after the first successful save.
Data we read
| New Relic data | Platform use |
|---|---|
| Open and closed alert issues | Quality metrics, MTTR, escaped-incident signals; SDLC Engineering Health “Time to Restore Service” |
| Deployment markers (when present) | DORA deployment frequency; SDLC Engineering Health “Deployment Frequency” |
| APM entity names (metadata on issues) | Heuristic repo matching in v1 |
We fetch roughly the last 30 days of issues and deployments on each sync (scheduled daily or when you click Sync now).
Data we do not read or change
The integration is read-only. We never create, update, or delete anything in your New Relic account.
| Not accessed | Notes |
|---|---|
| APM metrics, logs, or traces | No performance time series or log bodies |
| Alert policies or notification channels | Issues only, not policy definitions |
| Dashboards, NRQL queries, or synthetics | Not exported |
| Infrastructure or host inventory | Not scanned |
| Ingest or license keys | Connect uses a User API key only |
Repository Readiness observability scans (dimension E) remain repo-based; connecting New Relic improves live Quality/DORA metrics, not automatic readiness score bumps.
Sync schedule
After connect, the platform syncs on a daily batch schedule. Use Sync now in Integrations → New Relic for an immediate pull. You receive an in-app notification when a sync completes or fails.
SDLC Engineering Health (Insights)
Under Insights → Engineering Health, the platform reads the same weekly dashboard metrics New Relic sync writes. You do not connect New Relic twice.
| SDLC metric (when available) | Powered by New Relic when |
|---|---|
| Time to Restore Service (MTTR) | Alert issues were declared and resolved in the selected period |
| Deployment Frequency | Deployment markers exist in New Relic for the period |
| Change Failure Rate | Both incidents and deployments exist in the bucket |
If a tile shows unavailable, confirm New Relic has issues or deployment markers in the last ~30 days and run Sync now.
Other live monitoring connectors that feed the same Insights buckets:
- Prometheus (Alertmanager alerts → MTTR)
- Grafana (Unified Alerting + deploy annotations → MTTR and deployment frequency)
Disconnect
Remove New Relic under Integrations → Disconnect. Polling stops; previously ingested events remain in historical metrics until retention policies apply.