-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #18550 from newrelic/daily-release/Sep-3--2024-8_49
Daily release/sep 3 2024 8 49
- Loading branch information
Showing
54 changed files
with
1,240 additions
and
436 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
140 changes: 140 additions & 0 deletions
140
...ent/docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,140 @@ | ||
| --- | ||
| title: 'Create and modify Kubernetes alerts' | ||
| tags: | ||
| - Integrations | ||
| - Kubernetes integration | ||
| - Alerts | ||
| freshnessValidatedDate: 2024-09-02 | ||
| --- | ||
|
|
||
| With New Relic, you can stay informed about Kubernetes issues by defining the specific data you want to monitor, setting customizable [thresholds](/docs/alerts/create-alert/set-thresholds/set-thresholds-alert-condition/), and configuring the [notifications](/docs/alerts/get-notified/intro-notifications/) you want to receive. You can add a set of [recommended alert policies](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies) that you can tailor to your needs, or you can create completely custom <InlinePopover type="alerts"/>, policies, and [workflows](/docs/alerts/get-notified/incident-workflows/) to suit your environment. | ||
|
|
||
| <Callout variant="tip"> | ||
| Check out [Alerting concepts and terms](/docs/alerts/overview/#concepts-terms) for more information about how alerts work. | ||
| </Callout> | ||
|
|
||
|
|
||
| ## Create a Kubernetes alert condition [#create-k8s-alert-condition] | ||
|
|
||
| 1. Go to <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure**</DNT> and click <DNT>**Alerts**</DNT> on the left navigation pane. | ||
|
|
||
| 2. Click <DNT>**+ New Alert Condition**</DNT>. | ||
|
|
||
| <img | ||
| title="Kubernetes - new alert condition" | ||
| alt="Add Kubernetes alerts" | ||
| src="/images/kubernetes_screenshot-crop_new-alert-condition-button.webp" | ||
| /> | ||
|
|
||
| 3. Choose <DNT>**Kubernetes**</DNT> as an alert type and define your thresholds. | ||
|
|
||
| <img | ||
| title="Kubernetes - new alert condition" | ||
| alt="Add Kubernetes alerts" | ||
| src="/images/kubernetes_screenshot-crop_create_alert_condition.webp" | ||
| /> | ||
|
|
||
| 4. Define your [thresholds](/docs/alerts/create-alert/set-thresholds/set-thresholds-alert-condition/). | ||
|
|
||
| 5. Configure your [alert policy](/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](/docs/alerts/create-alert/condition-details/provide-runbook-instructions-alert-activity). | ||
|
|
||
| 8. Click <DNT>**Create**</DNT>. | ||
|
|
||
|
|
||
| <Callout variant="tip"> | ||
| You can also create Kubernetes alerts using a [NRQL alert condition](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/). | ||
| </Callout> | ||
|
|
||
|
|
||
| ## Create a Kubernetes alert policy [#create-k8s-alert-condition] | ||
|
|
||
| 1. Go to <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure**</DNT> and click <DNT>**Alerts**</DNT> on the left navigation pane. | ||
|
|
||
| 2. Click <DNT>**+ New alert policy**</DNT>. | ||
|
|
||
| <img | ||
| title="Kubernetes - new alert condition" | ||
| alt="Add Kubernetes alerts" | ||
| src="/images/kubernetes_screenshot-crop_new-alert-policy-button.webp" | ||
| /> | ||
|
|
||
| 3. Enter a [meaningful name](/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 incidents](/docs/alerts/organize-alerts/specify-when-alerts-create-incidents/#preference-options) from this policy. | ||
|
|
||
| 5. (Optional) Check the box <DNT>**Suppress noise with machine learning correlation**</DNT> to enable [correlation](/docs/alerts/organize-alerts/change-applied-intelligence-correlation-logic-decisions/) for the alert policy. | ||
|
|
||
| <img | ||
| width="40%;" | ||
| title="Kubernetes - new alert condition" | ||
| alt="Add Kubernetes alerts" | ||
| src="/images/kubernetes_screenshot-crop_create_alert_policy.webp" | ||
| /> | ||
|
|
||
| 6. Click <DNT>**Set up notifications**</DNT>. | ||
|
|
||
|
|
||
| ## Kubernetes alert notifications [#alert-notifications] | ||
|
|
||
| Once you've configured your alert conditions, policies, and [workflows](/docs/alerts/get-notified/incident-workflows/), you'll begin to receive notifications when the threshold configured in an alert condition is triggered. You have these options: | ||
|
|
||
| * [View the incident](/docs/alerts/incident-management/view-event-details-incidents/) | ||
|
|
||
| * [Acknowledge the incident](/docs/alerts/get-notified/acknowledge-alert-incidents/) | ||
|
|
||
| * 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: | ||
|
|
||
| * <DNT>**Available pods are less than desired pods**</DNT> alerts: | ||
|
|
||
| ``` | ||
| K8s:CLUSTER_NAME:PARENT_NAMESPACE:replicaset:REPLICASET_NAME | ||
| ``` | ||
|
|
||
| * <DNT>**CPU or memory usage**</DNT> alerts: | ||
|
|
||
| ``` | ||
| K8s:CLUSTER_NAME:PARENT_NAMESPACE:POD_NAME:container:CONTAINER_NAME | ||
| ``` | ||
|
|
||
| Here are some examples. | ||
|
|
||
| <CollapserGroup> | ||
| <Collapser | ||
| id="pod-alerts" | ||
| title="Pod alert notification example" | ||
| > | ||
| For <DNT>**Available pods are less than desired pods**</DNT> 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` | ||
| </Collapser> | ||
|
|
||
| <Collapser | ||
| id="container-resource" | ||
| title="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` | ||
| </Collapser> | ||
| </CollapserGroup> |
Oops, something went wrong.