For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Integrations
    • Collaboration tools
    • Data Export
    • Edge tools
    • Environments as a service
    • Experimentation and metric integrations
    • Internal developer platforms
    • Monitoring tools
      • AppDynamics
      • AWS CloudWatch RUM
      • Chronosphere
      • Datadog
      • Dynatrace
      • Elastic (ELK) Stack
      • Grafana
      • Honeycomb
      • Last9
      • Mezmo
      • New Relic One
        • Using the New Relic One events integration
        • Using flag triggers with New Relic One
      • PagerDuty for guarded rollouts
      • Splunk
      • Splunk Observability Cloud (formerly SignalFx)
    • Segments integrations
    • Workflow management tools
    • More integrations
    • Managing integrations
    • Using the LaunchDarkly integration framework
    • Building partner integrations
Sign inTry it free
LogoLogo
On this page
  • Prerequisites
  • Connect a flag trigger to New Relic One
  • Set up a JSON template in New Relic One
  • Connect the webhook to a New Relic One policy
  • Test the trigger configuration
IntegrationsMonitoring toolsNew Relic One

Using flag triggers with New Relic One

Was this page helpful?
Previous

PagerDuty for guarded rollouts

Next
Built with
Flag triggers are available to customers on select plans

Flag triggers are only available to customers on select plans. To learn more, read about our pricing. To upgrade your plan, contact Sales.

This topic explains how to use LaunchDarkly’s trigger feature with New Relic One. For example, you can create a policy in New Relic One that uses a LaunchDarkly trigger to toggle a flag’s targeting on or off if a performance metric drops below a certain threshold.

Prerequisites

In order to complete this topic, you must meet the following prerequisites:

  • You must have a feature flag with a trigger. To learn more about creating triggers, read Creating flag triggers.
  • You must have access to the trigger’s URL, which you copied and saved during the trigger creation process. To learn more, read Flag trigger security.
  • You must have an existing New Relic One account.

Connect a flag trigger to New Relic One

Connecting a LaunchDarkly trigger to New Relic One takes two steps.

You must:

  1. Create a webhook-type notification channel in New Relic One with your trigger URL, and
  2. Connect that webhook to a New Relic One policy.

Set up a JSON template in New Relic One

First you must configure a JSON template to use the LaunchDarkly trigger.

To configure the template:

  1. Log in to New Relic One.
  2. Navigate to “Alerts & AI” and find the “Notification Channels” section in the sidebar.
  3. In the “Notification Channels” section, click + New Notification Channel.
  4. Select Webhook as the channel type.
  5. Paste the LaunchDarkly trigger URL into the “Base URL” field.
  6. Click Create Channel.

Connect the webhook to a New Relic One policy

After you create the webhook notification channel in New Relic One, you must connect it to a policy in order for the LaunchDarkly trigger to perform actions on the flag.

  1. Under “Alerts & AI,” navigate to “Policies.”
  2. Select the policy you wish to connect to the trigger.
  3. On the policy’s “Notification channels” tab, add your newly-created webhook channel.

Test the trigger configuration

After you create a trigger in New Relic One, you can verify that it has connected to LaunchDarkly correctly.

To test the trigger:

  1. Navigate to the configuration for the webhook notification channel you set up in New Relic One.
  2. Click Send a test notification at the bottom of the page. A popup with a response code appears.
  3. Navigate back to the flag’s environment-specific settings page in LaunchDarkly.
  4. Click on the overflow menu on your LaunchDarkly trigger to confirm that the execution count has incremented. Sending a test notification does not trigger the flag action, so don’t worry that you might toggle a flag by testing the configuration.

When the conditions of your policy are met, your flag changes will now be performed.