Skip to main content

​
Overview

The New Relic integration enables Steadwing to access application performance monitoring (APM) data, infrastructure metrics, and observability insights from your New Relic account. During root cause analysis, Steadwing correlates performance metrics, transaction traces, and infrastructure data with production incidents.

​
Why Use New Relic with Steadwing?

APM Insights

Analyze application performance metrics and transaction traces

Infrastructure Monitoring

Track server metrics, container health, and resource utilization

Error Analysis

Correlate application errors with incident timing

Real-Time Metrics

Access real-time performance data during active incidents

​
Setup Instructions

​
Step 1: Create New Relic API Key

  1. Log in to your New Relic account
  2. Click on your user menu (bottom left corner)
  3. Navigate to API Keys
  4. Click Create a key
  5. Configure the key:
    • Key type: User Key
    • Name: Steadwing Integration
    • Account: Select your account
    • Notes: (Optional) API key for Steadwing RCA integration
  6. Click Create a key
  7. Copy the generated API key (starts with NRAK-)
Save your API key immediately! New Relic only shows it once. If you lose it, you’ll need to create a new key.

​
Step 2: Identify Your New Relic Region

Determine your New Relic region:
  • US Datacenter → Use region: US
    • API endpoint: api.newrelic.com
    • Typical for US-based accounts
  • EU Datacenter → Use region: EU
    • API endpoint: api.eu.newrelic.com
    • For EU-based accounts with data residency requirements
If unsure, check your New Relic URL:
  • one.newrelic.com → US
  • one.eu.newrelic.com → EU

​
Step 3: Connect New Relic in Steadwing

  1. Navigate to Steadwing Settings
  2. Find the New Relic integration card
  3. Click to expand the collapsible form
  4. Fill in the required fields:
    • API Key: Your New Relic User Key (starts with NRAK-)
    • Region: Enter either US or EU
  5. Toggle the switch to Enable the integration

​
Step 4: Verify Connection

  1. Return to Steadwing Settings
  2. Confirm the New Relic integration shows as Connected
  3. Create a test incident to verify metric data is being pulled correctly

​
How New Relic Integration Works

​
Data Collection

Steadwing queries New Relic for:
  • APM Metrics - Application response times, throughput, error rates
  • Transaction Traces - Slow transactions and database queries
  • Infrastructure Metrics - CPU, memory, disk, network usage
  • Error Events - Application exceptions and error details
  • Custom Events - Any custom instrumentation and metrics

​
Root Cause Analysis

When analyzing an incident, Steadwing:
  1. Identifies the incident time window
  2. Queries relevant APM and infrastructure data
  3. Analyzes transaction traces for performance bottlenecks
  4. Detects anomalies in error rates and response times
  5. Correlates metrics with deployments from GitHub
  6. Provides performance insights in the RCA report

​
Use Cases

Scenario 1: Slow API Response
  • Incident: API endpoint latency increased 5x
  • Steadwing finds: Database query time spiked in New Relic APM
  • Analysis: N+1 query pattern introduced in recent deployment
  • Solution: Optimize queries with proper indexing
Scenario 2: Memory Leak
  • Incident: Application instances crashing periodically
  • Steadwing finds: Gradual memory increase in infrastructure metrics
  • Analysis: Memory not being released after processing large files
  • Solution: Implement proper resource cleanup
Scenario 3: Service Dependency Issue
  • Incident: User authentication failing intermittently
  • Steadwing finds: External service call timeout rate increased
  • Analysis: Third-party auth provider degradation
  • Solution: Implement circuit breaker and fallback mechanism

​
Configuration

​
Required Permissions

The New Relic API Key must have:
  • metrics_read - Read time series metric data
  • events_read - Read event data and custom events
User Keys automatically include these permissions.

​
FAQs

Use a User Key (starts with NRAK-). This provides the necessary permissions for reading metrics and events. Do not use Ingest Keys or other key types.
Check your New Relic login URL. If you use one.newrelic.com, you’re on US. If you use one.eu.newrelic.com, you’re on EU. You can also check in Account Settings.
No, Steadwing only has read access. It queries metrics and events but never modifies data, dashboards, alert policies, or configurations.
Yes, the RCA report includes charts, transaction traces, and metric summaries that were analyzed during the investigation.
The integration will not work. User Keys don’t expire automatically, but if revoked or deleted, you’ll need to create a new key and update it in Settings.
Need additional help? Please reach out to us at [email protected]