---
title: Create and modify Kubernetes alerts
source: https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts
---

With New Relic, you can stay informed about Kubernetes issues by defining the specific data you want to monitor, setting customizable [thresholds](https://docs.newrelic.com/docs/alerts/create-alert/set-thresholds/set-thresholds-alert-condition/), and configuring the [notifications](https://docs.newrelic.com/docs/alerts/get-notified/intro-notifications/) you want to receive. You can add a set of [recommended alert policies](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies) that you can tailor to your needs, or you can create completely custom alerts, policies, and [workflows](https://docs.newrelic.com/docs/alerts/get-notified/alert-event-workflows/) to suit your environment.

> #### 💡 TIP
>
> Check out [Alerting concepts and terms](https://docs.newrelic.com/docs/alerts/overview/#concepts-terms) for more information about how alerts work.

## Create a Kubernetes alert condition [#create-k8s-alert-condition]

1.  Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure** and click **Alerts** on the left navigation pane.

2.  Click **+ New Alert Condition**.

    ![Add Kubernetes alerts](https://docs.newrelic.com/images/kubernetes_screenshot-crop_new-alert-condition-button.webp "Kubernetes - new alert condition")

3.  Choose **Kubernetes** as an alert type and define your thresholds.

    ![Add Kubernetes alerts](https://docs.newrelic.com/images/kubernetes_screenshot-crop_create_alert_condition.webp "Kubernetes - new alert condition")

4.  Define your [thresholds](https://docs.newrelic.com/docs/alerts/create-alert/set-thresholds/set-thresholds-alert-condition/).

5.  Configure your [alert policy](https://docs.newrelic.com/docs/alerts/organize-alerts/create-edit-or-find-alert-policy/). You can create a new policy or add this condition to an existing policy.

6.  Set the condition status of the condition.

7.  (Optional) Add a [runbook URL](https://docs.newrelic.com/docs/alerts/create-alert/condition-details/provide-runbook-instructions-alert-activity).

8.  Click **Create**.

> #### 💡 TIP
>
> You can also create Kubernetes alerts using a [NRQL alert condition](https://docs.newrelic.com/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/).

## Create a Kubernetes alert policy [#create-k8s-alert-condition]

1.  Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure** and click **Alerts** on the left navigation pane.

2.  Click **+ New alert policy**.

    ![Add Kubernetes alerts](https://docs.newrelic.com/images/kubernetes_screenshot-crop_new-alert-policy-button.webp "Kubernetes - new alert condition")

3.  Enter a [meaningful name](https://docs.newrelic.com/docs/alerts/organize-alerts/create-edit-or-find-alert-policy/#best-practices-policies) for the policy (maximum 64 characters).

4.  Choose the way you want to [group the alert events](https://docs.newrelic.com/docs/alerts/organize-alerts/specify-when-alerts-create-events/#preference-options) from this policy.

5.  (Optional) Check the box **Suppress noise with machine learning correlation** to enable [correlation](https://docs.newrelic.com/docs/alerts/organize-alerts/change-applied-intelligence-correlation-logic-decisions/) for the alert policy.

    /\*  \*/

6.  Click **Set up notifications**.

## Kubernetes alert notifications [#alert-notifications]

Once you've configured your alert conditions, policies, and [workflows](https://docs.newrelic.com/docs/alerts/get-notified/alert-event-workflows/), you'll begin to receive notifications when the threshold configured in an alert condition is triggered. You have these options:

-   [View the alert event](https://docs.newrelic.com/docs/alerts/alert-event-management/view-alert-event-details/)

-   [Acknowledge the alert event](https://docs.newrelic.com/docs/alerts/get-notified/acknowledge-alert-events/)

-   Go to a chart of the alert event data by selecting the name of the identifier. The entity identifier that triggered the alert appears near the top of the notification message. The format of the identifier depends on the alert type:

    -   **Available pods are less than desired pods** alerts:

        ```
          K8s:CLUSTER_NAME:PARENT_NAMESPACE:replicaset:REPLICASET_NAME
        ```

    -   **CPU or memory usage** alerts:

        ```
          K8s:CLUSTER_NAME:PARENT_NAMESPACE:POD_NAME:container:CONTAINER_NAME
        ```

    Here are some examples.

    **Pod alert notification example**

    For **Available pods are less than desired pods** alerts, the ID of the `ReplicaSet` triggering the issue might look like this:

    ````
    k8s:beam-production:default:replicaset:nginx-deployment-1623441481
    ```

    This identifier contains the following information:

    * Cluster name: `beam-production`
    * Parent namespace: `default`
    * `ReplicaSet` name: `nginx-deployment-1623441481`

    ````

    **Container resource notification example**

    For container CPU or memory usage alerts, the entity might look like this:

    ````
    k8s:beam-production:kube-system:kube-state-metrics-797bb87c75-zncwn:container:kube-state-metrics
    ```

    This identifier contains this information:

    * Cluster name: `beam-production`
    * Parent namespace: `kube-system`
    * Pod namespace: `kube-state-metrics-797bb87c75-zncwn`
    * Container name: `kube-state-metrics`

    ````