Daily release/sep 3 2024 8 49

src/content/docs/alerts/organize-alerts/specify-when-alerts-create-incidents.mdx

@@ -148,7 +148,7 @@ Each issue preference option has its own advantages. You can select any preferen
   </tbody>
 </table>
 
-## One issue per policy (default) [#preference-policy]
+### One issue per policy (default) [#preference-policy]
 
 Choose the <DNT>**One issue per policy**</DNT> preference if your policy and its conditions have a focused scope, like monitoring one entity.
 
@@ -166,7 +166,7 @@ If additional conditions open incidents after the issue opens, the incidents are
   When you select the default option <DNT>**One issue per policy**</DNT> as your issue preference, it will group all incidents opened by any condition on that policy into the same issue.
 </figcaption>
 
-## One issue per condition [#preference-condition]
+### One issue per condition [#preference-condition]
 
 Choose the <DNT>**One issue per condition**</DNT> option when you want an individual issue record to focus on a specific condition. If the policy has multiple conditions, you will see separate issue records for each condition on your <DNT>**Issues & activity**</DNT> page. Learn more about [your issue creation preferences](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#issue-creation).
 
@@ -186,7 +186,7 @@ Choose the <DNT>**One issue per condition**</DNT> option when you want an indivi
   When you select the option <DNT>**One issue per condition**</DNT> as your issue preference, it will group all incidents by any signal for a specific condition into separate issues.
 </figcaption>
 
-## One issue per condition and signal [#preference-signal]
+### One issue per condition and signal [#preference-signal]
 
 The <DNT>**One issue per condition and signal**</DNT> option is the most granular level for creating issue records. Choose this issue preference when you want to closely monitor anything that is occurring anywhere across your infrastructure.
 Learn more about [your issue creation preferences](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#issue-creation).

src/content/docs/alerts/troubleshooting/missing-alert-notifications.mdx

@@ -74,7 +74,7 @@ Here are some tips to avoid being placed on our suppression list:
       </td>
 
       <td>
-        In general, email isn’t the most reliable way to receive notifications. For your most important alerts, set up [alternate means of communication](/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts#channel-types) as a backup.
+        In general, email isn't the most reliable way to receive notifications. For your most important alerts, set up [alternate means of communication](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/) as a backup.
       </td>
     </tr>
   </tbody>

src/content/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels.mdx

@@ -7,6 +7,7 @@ tags:
   - Notification Channels
 metaDescription: 'For New Relic alerts: how you can list, create, update, and delete channels with our NerdGraph API.'
 redirects:
+  - /docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts
 freshnessValidatedDate: never
 ---
 

src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx

@@ -160,6 +160,6 @@ To learn more about exploring your Kubernetes data, check out these docs:
 
   <DocTile
     title="Set alerts on Kubernetes"
-    path="/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy"
+    path="/docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts"
   />
 </DocTiles>

src/content/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx

@@ -53,7 +53,7 @@ Take a look at what you can do with New Relic:
 
 * Scrape Prometheus metrics from any workload in the cluster thanks to the service discovery provided by the [Prometheus Agent](/docs/infrastructure/prometheus-integrations/get-started/send-prometheus-metric-data-new-relic/#Agent).
 
-* Create [alert policies](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) and [alert conditions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) based on your Kubernetes data, or extend the [predefined alert conditions](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy).
+* The integration includes a set of [predefined alert conditions](/docs/kubernetes-pixie/kubernetes-integration/installation/predefined-alert-policy), but you can [create and modify your Kubernetes alerts](/docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts) based on your Kubernetes data, or add a set of [recommended alert policy](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policy). 
 
 * Check out all your Kubernetes events. The [Kubernetes events integration](/docs/integrations/kubernetes-integration/kubernetes-events/install-kubernetes-events-integration) watches for events happening in your Kubernetes clusters and sends those events to New Relic. You can then visualize the event data in the cluster explorer. It's installed by default after [installing the New Relic Kubernetes integration](/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure/).
 

src/content/docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts.mdx

@@ -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>