---
title: Alerts for infrastructure: Add, edit, or view host alert information
source: https://docs.newrelic.com/docs/infrastructure/infrastructure-alerts/infrastructure-alerts-add-edit-or-view-host-alert-information
---

With New Relic's infrastructure monitoring, you can create [alert conditions](https://docs.newrelic.com/docs/alerts/new-relic-alerts/getting-started/alerts-glossary#alert-condition) directly within the context of what you're currently monitoring with New Relic.

For example, if you've used the [filter bar](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities) to filter to a specific set of hosts, and you notice a problem, you can create an alert from the infrastructure UI. To create the alert, select a saved filter view, and tailor the alert condition directly from the chart you're viewing. This helps you proactively manage and monitor the alerting system for your environment.

Want to try out alert conditions with our infrastructure agent? [Create a New Relic account](https://newrelic.com/signup) for free! No credit card required.

## Create alert conditions for infrastructure [#create-condition]

Alert conditions apply to alert [policies](https://docs.newrelic.com/docs/alerts/new-relic-alerts/getting-started/alerts-glossary#alert-policy). You can select an existing policy or create a new policy with email notifications from our infrastructure UI. If you want to use other types of [notification channels](https://docs.newrelic.com/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-controlling-where-send-alerts), create a [new policy](https://docs.newrelic.com/docs/alerts/new-relic-alerts/configuring-alert-policies/name-or-rename-alert-policy) from within the alerts UI.

> #### ⚠️ IMPORTANT
>
> The Infrastructure REST API has a limit of 3,700 alert conditions, including both active **and** disabled conditions. The API, whether used directly or via the UI, will reject all requests to add any additional alert conditions beyond the 3,700 alert condition limit.

To add an infrastructure alert condition to an alerts policy:

1.  Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure**. Mouse over a chart you want to alert on, select the ellipses  icon, and then select **Create alert condition**.
2.  Type a meaningful condition name.
3.  Select the **Alert type**, or refer to the [examples](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/infrastructure-alert-conditions/infrastructure-alerting-examples) to decide which type to select.
4.  Create individual filters, or copy all the filters from the [entity filter bar](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/core-concepts/search-filter-entities) to identify the hosts that you want the alert condition to use.
5.  Define the **Critical** (required) and **Warning** (optional, if available) [thresholds](https://docs.newrelic.com/docs/alerts/new-relic-alerts/getting-started/alerts-glossary#alert-threshold) for triggering the alert notification.
6.  Optional: To create the condition criteria proactively but not receive alert notifications at this time, turn off the [**Enabled** checkbox option](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/infrastructure-alerts-add-edit-or-view-host-alert-information#enabled).
7.  Select an existing policy for the new condition.

    OR

    Select the option to create a new policy and identify the email for alert notifications.
8.  Optional: Add a [runbook url](#runbook-url-infrastructure).
9.  Optional: Set the [**Close open alert events after**](#alert-event-time-limit) time limit to automatically close open alert events after a certain amount of time (this defaults to 24 hours for infrastructure conditions).
10. Select **Create**.

> #### ⚠️ IMPORTANT
>
> If New Relic hasn't received a cloud integration service's attribute in the past 60 minutes, we refer to this as a "silent attribute," and it won't be available to use as an alert condition in the UI. In this situation, you can use the [API](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/infrastructure-alert-conditions/rest-api-calls-new-relic-infrastructure-alerts/) to create alert conditions for silent attributes.

## Other infrastructure alert condition methods [#methods]

You can also use these other methods to create an infrastructure alert condition:

**Use the alerts UI**

Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Alert policies > New alert policy > Create new condition**, then select **Infrastructure** as the product.

**Use the Infrastructure UI**

1.  Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Hosts**.
2.  Mouse over the chart you want to alert on, select the ellipses  icon, and then select **Create alert**.

**Use infrastructure settings for integrations**

> #### 💡 TIP
>
> Use this method to create an alert condition for infrastructure integrations.

1.  Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Settings > Alerts**, and then click **Create alert condition**.
2.  Name and describe the alert condition.
3.  Click the **Integrations** alert type, and then select the integration data source you'd like to use.
4.  Use the **Filter entities** dropdown to limit your condition to specific attributes.
5.  Use the **Define thresholds** dropdowns to define your condition's thresholds, and then click **Create**.

    The configuration settings are optional. You can always update them later.

## View host alert events [#view-alerts]

Anyone included in the policy's [notification channels](#notification) receive alert notifications directly. In addition, anyone with permissions for your New Relic account can view infrastructure alert events and individual alert events through the user interface.

1.  Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Events**.
2.  To change the hosts or time frame, use the search window, entity filter bar, or time functions.
3.  From the **Events** list, select the alert event.
4.  To [view detailed information in alerts](https://docs.newrelic.com/docs/alerts/alert-event-management/view-alert-event-details) about the selected alert event, select the link.

## Update or delete host alert information [#maintain-alerts]

To edit, disable (or re-enable), or delete host alert information:

1.  Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Settings > Alerts**.
2.  Optional: Use the search window or **Select all** checkbox to locate one or more alert conditions.
3.  Select any of the available functions to 
    edit, disable, enable, or 
    delete the selected conditions.

## Use alerts to monitor your entire infrastructure [#nr-alerts]

[Alerts](https://docs.newrelic.com/docs/alerts/new-relic-alerts-beta/getting-started/new-relic-alerts) provides a single, coordinated alerting tool across all of your New Relic products. This allows you to manage [alert policies](https://docs.newrelic.com/docs/alerts/overview#alert-policy) and [conditions](https://docs.newrelic.com/docs/alerts/overview#alert-condition) that focus on the metrics for [entities](https://docs.newrelic.com/docs/alerts/overview#alert-entity) that you care about the most, such as Docker containers, JVMs, and more.

| **Alert features**    | **Features in infrastructure monitoring**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Alert conditions      | - Create: Use the [Infrastructure](#create-condition) UI. - View, change, disable (or re-enable), or delete: Use the [Infrastructure **Settings > Alerts**](#maintain-alerts) UI.                                                                                                                                                                                                                                                                                                                                                                                                            |
| Information on alerts | - View summary information about [events](https://docs.newrelic.com/docs/alerts/new-relic-alerts/getting-started/alerts-glossary#event): Use the [Infrastructure **Events**](#view-alerts) UI. - View detailed information about [alert events](https://docs.newrelic.com/docs/new-relic-solutions/get-started/glossary#alert-event): Use the [alerts](https://docs.newrelic.com/docs/alerts/alert-event-management/view-alert-event-details) UI or the [notification channel](#notification) integrated with the associated policy.                                                         |
| Alert policies        | View, add, change, disable, or delete: - For policies with a variety of notification channels: Use the [alerts](https://docs.newrelic.com/docs/alerts/new-relic-alerts/updating-alert-policies/change-alert-policies) UI. - For policies only needing [email notifications](#notification): Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Settings > Alerts > Create a new policy**, and add one or more email addresses as needed. Add host conditions to an existing policy: Use the [Infrastructure](#create-condition) UI. |
| Notification channels | To view, add, change, or delete [available notification options](#notification): - Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Settings > Alerts**. - Optional: Search for the condition or policy name. - From the list of conditions, select the policy link to view notification channel information in the alerts UI.                                                                                                                                                                                                    |

## Add a description [#description]

The use of the **Description** field is available for these alert condition types:

-   NRQL conditions: add a description using the [NerdGraph API](https://docs.newrelic.com/docs/alerts/alerts-nerdgraph/nerdgraph-examples/nerdgraph-api-alerts-nrql-conditions).
-   Infrastructure conditions: add a description using the UI or the REST API.

The text you place in an alert condition's **Description** field is passed downstream to associated alert events and notifications. A description can be used for several purposes, including:

-   Capturing the reason for the alert condition.
-   Defining the signal being monitored.
-   Defining next steps.
-   Add metadata to downstream systems.

You can use template substitution to insert values from the attributes in the associated alert event event. The template format is `{{attributeName}}`. For the attributes you can use when creating a description, see [alert event attributes](https://docs.newrelic.com/docs/alerts/create-alert/condition-details/alert-event-attributes).

One available attribute is the special `{{tag.*}}` attribute. This attribute prefix is used to access any of the tag values that are included with the target signal, or any of the entity tags that are associated with the target signal.

If there are entity tags associated with your alert event, then they can be accessed using the entity tag name. An example of this would be `{{tag.aws.awsRegion}}`. When entity tags are available to use, you see them included with the alert event, and displayed when you view the alert event.

This field has a maximum character size of 4,000.

## Add or edit a runbook URL [#runbook-url-infrastructure]

The [alert condition creation process](#create-condition) includes an option for setting a URL for runbook instructions. This lets you link to information or standard procedures for handling an alert event. Before adding or updating the link, make sure you use a valid URL.

To add, update, or delete an alert condition's runbook URL:

1.  Select an alert condition, and make changes to the **Runbook URL** link.
2.  Save the condition.

In order to be saved, the URL must be a valid URL.

## alert event time limit [#alert-event-time-limit]

The alert event time limit allows you to define a time period after which alert events will be force-closed. By default, alert event time limit is 24 hours for insfrastructure conditions.

To add or update an alert condition's alert event time limit:

1.  Select an alert condition, and make changes to the alert event time limit.
2.  Save the condition.

## Alert conditions that generate too-long NRQL queries [#alert-nrql-error]

Alert conditions created for infrastructure rely on behind-the-scenes NRQL queries, and NRQL queries have a 4096-character limit. This means that if your condition generates a very complex NRQL query that filters on many elements (for example, including many hosts or many tags), it will exceed this limit and display an error message saying that the condition failed.

To solve this problem, reduce the number of elements you are using in your alert condition. For example:

| Problem  | Solution                                                                                                                                                                                                                                                                              |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Hosts    | - If you entered a large number of hosts that caused the condition to fail, reduce the number of hosts. - Use substrings to target hosts. For example, instead of targeting `prod-host-01`, `prod-host-02`, and `prod-host-03`, just target all hosts with `prod-host-0` in the name. |
| Entities | - Edit your alert condition to target specific attributes that apply to the entities you're trying to target. - Create custom attributes for the entities you want to target, and use those attributes in your alert condition.                                                       |

For more information, see [Best practices for filtering in infrastructure alerts](https://support.newrelic.com/s/hubtopic/aAX8W0000008Zfu/relic-solution-best-practice-for-filtering-in-infrastructure-alerts) in New Relic's Support Forum.