New Relic Terraform Provider

The newrelic_one_dashboard_raw resource allows you to create and manage New Relic One dashboards using a RawConfiguration.

Warning: The newrelic_one_dashboard_json resource is preferred for configuring dashboards. newrelic_one_dashboard_raw does not support the latest dashboard features and receives less investment from New Relic.

resource "newrelic_one_dashboard_raw" "exampledash" {
  name = "New Relic Terraform Example"

  page {
    name = "Page Name"
    widget {
      title = "Custom widget"
      row = 1
      column = 1
      width = 1
      height = 1
      visualization_id = "viz.custom"
      configuration = <<EOT
      {
        "legend": {
          "enabled": false
        },
        "nrqlQueries": [
          {
            "accountId": ` + accountID + `,
            "query": "SELECT average(loadAverageOneMinute), average(loadAverageFiveMinute), average(loadAverageFifteenMinute) from SystemSample SINCE 60 minutes ago    TIMESERIES"
          }
        ],
        "yAxisLeft": {
          "max": 100,
          "min": 50,
          "zero": false
        }
      }
      EOT
    }
  }
}

The newrelic_fleet_members resource manages which entities are assigned to one or more rings within a specific New Relic Fleet.

Membership Model

This resource uses an opt-in management model. It only tracks and manages the entities explicitly listed in the entity_ids argument of each ring block.

Entities can enter a fleet ring via two paths:

1. Agent Control instrumentation: Automatic assignment via the platform. These entities are invisible to Terraform and are not managed by this resource unless you explicitly add them to entity_ids.
2. Explicit assignment: Managed via this resource using the FleetControlAddFleetMembers and FleetControlRemoveFleetMembers API mutations.

Key Behaviors

• Adopting Agent Control entities: To bring an entity managed by Agent Control under Terraform control, add its GUID to the entity_ids list. You will see a warning that the entity was skipped during the add mutation, but it will be adopted into the Terraform state on the next read. Once adopted, removing the GUID from your configuration will remove the entity from the ring.
• Drift: If an entity listed in entity_ids is removed from the ring via an external process (out-of-band), Terraform will issue a warning and attempt to re-add it on the next apply. To stop Terraform from re-adding it, remove the GUID from your configuration.
• Permissions: This resource requires the provider's API key to have Fleet Control permissions.

resource "newrelic_fleet_members" "example" {
  fleet_id = newrelic_fleet.example.id

  ring {
    name       = "default"
    entity_ids = [
      "MXxOR0VQfEhPU1R8MTIzNDU2Nzg",
      "MXxOR0VQfEhPU1R8ODc2NTQzMjE",
    ]
  }
}

By default, the data source looks for destinations within the account scope linked to your API key. To access account-scoped or cross-account (Organization-scoped) destinations, you must provide the scope argument.

The scope block requires:

• type: Either ORGANIZATION or ACCOUNT.
• id: The Organization UUID (if type is ORGANIZATION) or the New Relic account ID (if type is ACCOUNT).

# Creating a cross-account destination
resource "newrelic_notification_destination" "foo-destination" {
  name           = "webhook-example-cross-account-destination"
  type           = "WEBHOOK"

  property {
    key   = "source"
    value = "{\n\t\"name\": \"foo\"\n}"
    label = "Payload Template"
  }

  scope {
    type = "ORGANIZATION"
    id   = "00000000-0000-0000-0000-000000000000"
  }
}

# Looking up a cross-account destination
data "newrelic_notification_destination" "foo-destination" {
  id = "destination_id"

  scope {
    type = "ORGANIZATION"
    id   = "organization_id"
  }
}

New Relic is deprecating the legacy runtime for Synthetic monitors. If your monitors are not updated to the new runtime before the EOL dates, they may fail to run Synthetic checks.

Key EOL Dates:

• August 18, 2026: Node browser runtime monitors (Scripted Browser).
• November 18, 2026: Node API runtime monitors (Scripted API).

Implications for Terraform users: If you manage monitors via Terraform and do not update your configuration to use the new runtime attributes before the EOL:

1. Drift: After the EOL, New Relic will force-upgrade monitors to the new runtime via the API. Running terraform plan will show a drift because the actual state in New Relic no longer matches your legacy configuration.
2. Errors: Running terraform apply without updating your configuration to the new runtime values will result in an API error stating that usage of the legacy runtime is no longer supported.

By default, newrelic_entity searches for entities and filters them using the account_id specified in your provider configuration.

To retrieve an entity belonging to a specific subaccount (even if using a parent account's API key), use the account_id argument within the data source. This overrides the provider's default account filter.

Note on accountId tag vs account_id argument:

• The account_id argument filters the final result returned by the data source.
• Adding a tag with the key accountID adds that ID to the NRQL query sent to NerdGraph, filtering the API response itself. The final entity returned will still be subject to the account_id argument or provider configuration.

# Retrieve an entity from a specific subaccount
data "newrelic_entity" "app" {
  name       = "my-app"
  account_id = 654321
  domain     = "APM"
  type       = "APPLICATION"
}

# Using a subaccount created via newrelic_account_management
data "newrelic_entity" "app" {
  account_id = newrelic_account_management.default.id 
  name       = "my-app"
  domain     = "APM"
  type       = "APPLICATION"
}