Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase Crashlytics
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Set up
  • Navigate to the Integration settings view
  • Connect New Relic
  • Configure New Relic

Was this helpful?

  1. Integrations
  2. Observability & analytics

New Relic

PreviousMixpanelNextCustom observability & analytics

Last updated 5 days ago

Was this helpful?

Set up

Navigate to the Integration settings view

  1. Select an app in the top left corner from the Switcher

  2. Navigate to App Settings by clicking the gear icon (⚙️) at the top of the Timeline sidebar

  3. Click on Integrations in the sidebar

Connect New Relic

  1. Find the New Relic integration module under the Observability & analytics section

  2. Click the Connect button.

  3. If you've previously connected a New Relic integration for stability monitoring, you can use the same provider to connect New Relic for the observability & analytics capability. Alternatively, you can create a new installation by following the steps below.

New Relic API keys are scoped at the user level. The user that generates the API key must have the following roles:

  • Mobile Applications

  • Mobile Crashes

  1. Click Save to finish adding the integration provider.

Configure New Relic

  1. Select the application that's associated with your Production environment.

  2. Select key events from your New Relic application to monitor in Runway.

    1. For custom events, the value you enter in the Event field should be the event type and event name with a '#' delimiter in between. For example, Action#ClickButton.

    2. For each event, you can optionally use the Attribute field to specify an event attribute (e.g. amount) to track attribute value-related metrics such as averages, medians, and percentiles. Alternatively, you can also use the Attribute field to filter events using basic query string syntax: for example, if you have a page_load event and want to measure unsuccessful loads on a "checkout" screen, you might enter name=checkout&success=false for the Attribute value.

Click New installation and enter an API key. You can create a New Relic API key by going to Profile > API Keys. .

For more information about New Relic user permissions, visit their .

By default, Runway will create a handful of using the events you select as part of the integration setup to surface in the view of each release. You can further customize and configure these health metrics, including setting acceptable thresholds, connect them to and more!

For a complete list of all available metrics , visit the .

⚙️
🔗
New Relic API key documentation
docs
health metrics
Rollout
Metric Types documentation
rollout automations