• EnglishEspañol日本語한국어Português
  • Log inStart now

Create and modify Kubernetes alerts

With New Relic, you can stay informed about Kubernetes issues by defining the specific data you want to monitor, setting customizable thresholds, and configuring the notifications you want to receive. You can add a set of recommended alert policies that you can tailor to your needs, or you can create completely custom , policies, and workflows to suit your environment.

Tip

Check out Alerting concepts and terms for more information about how alerts work.

Create a Kubernetes alert condition

  1. Go to one.newrelic.com > All capabilities > Infrastructure and click Alerts on the left navigation pane.

  2. Click + New Alert Condition.

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

  4. Define your thresholds.

  5. Configure your 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.

  8. Click Create.

Tip

You can also create Kubernetes alerts using a NRQL alert condition.

Create a Kubernetes alert policy

  1. Go to one.newrelic.com > All capabilities > Infrastructure and click Alerts on the left navigation pane.

  2. Click + New alert policy.

  3. Enter a meaningful name for the policy (maximum 64 characters).

  4. Choose the way you want to group the incidents from this policy.

  5. (Optional) Check the box Suppress noise with machine learning correlation to enable correlation for the alert policy.

  6. Click Set up notifications.

Kubernetes alert notifications

Once you've configured your alert conditions, policies, and workflows, you'll begin to receive notifications when the threshold configured in an alert condition is triggered. You have these options:

  • View the incident

  • Acknowledge the incident

  • Go to a chart of the incident 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.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.