Merge pull request #13089 from newrelic/issues-are-created

feat(Alerts): Updated the entire page

src/content/docs/alerts-applied-intelligence/applied-intelligence/postmortems-applied-intelligence.mdx

@@ -57,7 +57,7 @@ When an issue is closed, you can create a postmortem.
 
 To find your issues, go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Analyze**, and click **Issues & activity**.
 
-Issues are groups of incidents related to the same underlying problem. When a new incident is created, incident intelligence opens an issue and evaluates other open issues for possible correlation.
+Issues are groups of incidents related to the same underlying problem. When a new incident is created, incident intelligence may open a new issue and evaluates other open issues for possible correlation. 
 
 Follow these steps to create a postmortem.
 

src/content/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents.mdx

@@ -17,7 +17,7 @@ redirects:
 
 import alertsIncidentPreferenceUi from 'images/alerts_screenshot-full_incident-preference-ui.webp'
 
-import alertsIncidentPreferenceOptions from 'images/alerts_screenshot-full_incident-preference-options.webp'
+import alertsIncidentPreferenceOptions from 'images/alerts_screenshot-crop_incident-preference-options.webp'
 
 import alertsByPolicy from 'images/alerts_diagram_by-policy.webp'
 
@@ -26,25 +26,64 @@ import alertsByCondition from 'images/alerts_diagram_by-condition.webp'
 import alertsBySignal from 'images/alerts_diagram_by-signal.webp'
 
 <Callout variant="important">
-  In this document, we use the new terms "issue" and "incident." Please see [this article](https://discuss.newrelic.com/t/new-terminology-coming-for-alerts/163727) for a full explanation of these new terms.
+  In this document, we use the new terms "issue" and "incident." Please see [this article](https://discuss.newrelic.com/t/new-terminology-coming-for-alerts/163727) for a full explanation of these terms.
 </Callout>
 
-An issue is a collection of one or more incidents.
+To make the most of the info on this page, we recommend understanding the meaning of these terms:
 
-Issues determine when you are notified about incidents disrupting your business. These incidents occur when your given alert conditions (like CPU overage, synthetic monitoring crashes, or slow web app response times) are met.
+* **Issues**. Issues are groups of incidents related to the same underlying problem. When a new incident is created, incident intelligence may open a new issue and evaluates other open issues for possible correlation. See [Issues and incident management and response](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/Issues-and-Incident-management-and-response/) for more information.
 
-Control which policy conditions create issues. This ensures that you are notified about important ongoing or recurring problems and not bombarded by unnecessary notifications.
+* **Incidents**. Incidents are events that describe the symptoms affecting your system over time. See [View violation and event details for incidents](/docs/alerts-applied-intelligence/new-relic-alerts/alert-incidents/view-violation-event-details-incidents/) for more information.
+
+* **Conditions**. A condition describes a monitored data source and the behavior of that data source that will be considered an incident. See [Create conditions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/) for more information.
+
+* **Policies**. A policy is a group of one or more conditions. See [Manage your policies](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) for more information.
+
+Issues determine when you're notified about incidents disrupting your business. These incidents occur when they meet your alert conditions. For example, you can have alert conditions about CPU overage, synthetic monitoring crashes, or slow web app response times.
+
+When you can control the policy conditions that create issues, you make sure that you're notified about important ongoing or recurring problems. This way you won't be bombarded with unnecessary notifications and avoid noise.
 
 Learn how to set issue preferences by your policy, condition, or condition and signal combination.
 
+## Select your issue preference [#preference-procedures]
+
+By default, a single issue record is created for each policy.
+
+To change the issue preference for the selected policy:
+
+1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (policies)**.
+2. Select a policy.
+
+<img
+  title="A screenshot showing where the issue preference button is inside the alerts user interface."
+  alt="A screenshot showing where the issue preference button is inside the alerts user interface."
+  src={alertsIncidentPreferenceUi}
+/>
+
+<figcaption>
+  Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (policies) > (select a policy)**. The selected policy page shows how alerts rolls up issues for alert notifications and UI details. The default option is **One issue per policy**. To choose a different option for this policy, click **Issue creation preference**.
+</figcaption>
+
+3. Click **Issue creation preference**, select your choice of available [options](#preference-options), and then **Save**.
+
+<img
+  width="60%;"
+  class="center"
+  title="A screenshot showing how to change your issue preferences on the alerts user interface."
+  alt="A screenshot showing how to change your issue preferences on the alerts user interface."
+  src={alertsIncidentPreferenceOptions}
+/>
+
+Repeat these steps for each policy as needed.
+
 ## Critical and warning incidents [#incident-types]
 
 Choose from two threshold types when a policy condition is met:
 
 * Critical (red)
 * Warning (yellow)
 
-When a policy condition violates a threshold, an incident is opened and an issue record can be created with detailed information to help you respond efficiently. The issue record may also include any other incidents occurring after the opening incident.
+When a policy condition breaches a threshold, an incident is opened and an issue record can be created with detailed information to help you respond efficiently. The issue record may also include any other incidents occurring after the opening incident.
 
 Notifications are sent to every notification channel on the policy as well as all destinations on any workflow that is properly configured when an issue opens, if and when an issue is acknowledged, and when an issue closes.
 
@@ -55,12 +94,16 @@ Each issue preference option has its own advantages. You can select any preferen
 <table>
   <thead>
     <tr>
-      <th width={200}>
-        **Issue preference**
+      <th>
+        Issue preference
       </th>
 
       <th>
-        **Advantages**
+        Description
+      </th>
+
+      <th>
+        Advantages
       </th>
     </tr>
   </thead>
@@ -73,7 +116,9 @@ Each issue preference option has its own advantages. You can select any preferen
 
       <td>
         Only one issue will be open at a time for the entire policy.
+      </td>
 
+      <td>
         * Fewest number of notifications
         * Requires immediate action and closing the issues to be effective
       </td>
@@ -86,102 +131,83 @@ Each issue preference option has its own advantages. You can select any preferen
 
       <td>
         One issue will be open at a time for each condition in your policy.
+      </td>
 
+      <td>
         * More notifications
-        * Useful for policies containing conditions that focus on [entities](/docs/apm/new-relic-apm/getting-started/glossary#alert-target) that perform the same job; for example, hosts that all serve the same application(s)
+        * Useful for policies containing conditions that focus on [entities](/docs/new-relic-solutions/get-started/glossary/#alert-signal) that perform the same job; for example, hosts that all serve the same application(s)
       </td>
     </tr>
 
     <tr>
       <td>
-        [One issue per incident](#preference-target)
+        [One issue per condition and signal](#preference-signal)
       </td>
 
       <td>
-        An issue will be created for every incident in your policy.
+        This option groups the incidents sharing the same condition and signal into their own issue.
+      </td>
 
+      <td>
         * The most notifications
-        * Useful if you need to be notified of every incident or if you have an external system where you want to send alert notifications
+        * Useful if you need a notification about any entity that creates an incident or if you have an external system where you want to send alert notifications
       </td>
     </tr>
   </tbody>
 </table>
 
-## Select your issue preference [#preference-procedures]
-
-By default, a single issue record will be created for each policy.
-
-To change the issue preference for the selected policy:
-
-1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (Policies)**, and then (**select a policy)**.
-2. Click **Issue creation preference**, select your choice of available [options](#preference-options), and then save.
-
-Repeat these steps for each policy as needed.
-
-<img
-  title="A screenshot showing where the issue preference button is inside the alerts user interface."
-  alt="A screenshot showing where the issue preference button is inside the alerts user interface."
-  src={alertsIncidentPreferenceUi}
-/>
-
-<img
-  title="A screenshot showing how to change your issue preferences on the alerts user interface."
-  alt="A screenshot showing how to change your issue preferences on the alerts user interface."
-  src={alertsIncidentPreferenceOptions}
-/>
+## One issue per policy (default) [#preference-policy]
 
-<figcaption>
-  **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert conditions (Policies) > (select a policy):** The selected policy page shows how alerts rolls up issues for alert notifications and UI details. (Default is **By policy**). To choose a different option for this policy, click **Issue creation preference**.
-</figcaption>
+Choose the **One issue per policy** preference if your policy and its conditions have a focused scope, like monitoring one entity.
 
-## One issue per policy (default) [#preference-policy]
+If additional conditions open incidents after the issue opens, the incidents are added to the same issue. You will only see one issue on your **Issues & activity** page for the selected policy. Learn more about [your issue creation preferences](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#issue-creation).
 
 <img
-  title="A diagram showing how the By policy issue preference works"
-  alt="A diagram showing how the By policy issue preference works"
+  width="40%;"
+  class="center"
+  title="A diagram showing how the **One issue per policy** option works"
+  alt="A diagram showing how the **One issue per policy** option works"
   src={alertsByPolicy}
 />
 
 <figcaption>
-  When you select the default (**One issue per policy**) as your issue preference, it will group all condition incidents into the same issue.
+  When you select the default option **One issue per policy** as your issue preference, it will group all incidents opened by any condition on that policy into the same issue.
 </figcaption>
 
-If additional conditions open incidents after the issue opens, the incidents are added to the same issue. Only one issue appears on your **Issues & activity** page for the selected policy.
+## One issue per condition [#preference-condition]
 
-Choose the **One issue per policy** preference if your policy and its conditions have a focused scope (like monitoring one entity). Learn more about [issue preference best practices](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#incident-practices).
+Choose the **One issue per condition** 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 **Issues & activity** page. Learn more about [your issue creation preferences](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#issue-creation).
 
-## One issue per condition [#preference-condition]
+* If a signal breaches a condition's threshold, an incident opens and it creates an issue record.
+* If the same signal breaches another condition's threshold, another incident opens and another issue record is created.
+* If additional signals open incidents on the same condition after the issue opens, these incidents are added to the issue record already opened for that condition.
 
 <img
-  title="A diagram showing how the By condition issue preference works"
-  alt="A diagram showing how the By condition issue preference works"
+  width="40%;"
+  class="center"
+  title="A diagram showing how the **One issue per condition** option works"
+  alt="A diagram showing how the **One issue per condition** option works"
   src={alertsByCondition}
 />
 
 <figcaption>
-  When you select **One issue per condition** as your issue preference, it will group all incidents by any target for a specific condition into separate issues.
+  When you select the option **One issue per condition** as your issue preference, it will group all incidents by any signal for a specific condition into separate issues.
 </figcaption>
 
-Choose the **One issue per condition** option when you want an individual issue record to focus on a specific condition. If the policy has multiple conditions, separate issue records for each condition will appear on your **Issues & activity** page.
-
-* If a target violates a condition for the alert policy, an incident will open and an issue record will be created.
-* If the same target violates another condition for the alert policy, another incident will open and another issue record will be created.
-* If additional targets open incidents on the same condition after the issue opens, these incidents will be added to the issue record already open for that condition.
 
-Learn more about [issue preference best practices](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#incident-practices).
+## One issue per condition and signal [#preference-signal]
 
-## One issue per incident [#preference-target]
+The **One issue per condition and signal** 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).
 
 <img
-  title="Alert policy issue preferences"
-  alt="Alert policy issue preferences"
+  width="40%;"
+  class="center"
+  title="A diagram showing how the **One issue per condition and signal** option works"
+  alt="A diagram showing how the **One issue per per condition and signal** option works"
   src={alertsBySignal}
 />
 
 <figcaption>
-  When you select **One issue per incident** as your issue preference, it will not group incidents at all. A new issue will be created for every incident that occurs in your policy.
+  When you select **One issue per condition and signal** as your issue preference, it will group incidents sharing the same condition and signal into their own issue. If the same signal on a condition opens another incident after an issue opens (for example, a warning incident may open, followed by a critical incident a short time later on the same signal), that new incident is added to the same issue. You will only see one issue on your **Issues & activity** page for the selected condition/signal combination.
 </figcaption>
-
-The **One issue per incident** 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 [issue preference best practices](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#incident-practices).

src/content/docs/alerts-applied-intelligence/new-relic-alerts/get-started/alerts-ai-overview-page.mdx

@@ -228,7 +228,7 @@ Click an issue to open its issue page.
 
 ## Incidents
 
-On the **Issues & activity** page, incidents are groups of events that describe the symptoms affecting your system over time. These symptoms are detected by your monitoring tools, which evaluate your data streams and events.
+On the **Issues & activity** page, incidents are events that describe the symptoms affecting your system over time. These symptoms are detected by your monitoring tools, which evaluate your data streams and events.
 
 New Relic incident metadata comes from any of the following sources:
 - Inheriting all the tags from the alert condition that triggered it