Merge pull request #2877 from newrelic/DOC-7075-Streaming-Alerts

Updating Streaming Alerts diagram

src/content/docs/alerts-applied-intelligence/new-relic-alerts/get-started/streaming-alerts-key-terms-concepts.mdx

@@ -18,10 +18,10 @@ The NRQL query provides the [signal filter](/docs/using-new-relic/welcome-new-re
 
 Alerts violations are easy when they're caused by a specific event happening, but trickier when looking for events not happening.
 
-![streaming_alerts.png](./images/streaming_alerts.png "streaming_alerts.png")
+![A diagram that demonstrates how data is streamed into New Relic.](./images/streaming-alerts.png "A diagram that demonstrates how data is streamed into New Relic.")
 
 <figcaption>
-  Only data that matches the conditions of the NRQL WHERE clause is alerted on.
+  Only data that matches the conditions of the NRQL WHERE clause is alerted on. For more details on each step of the process, see [Streaming alerts process and descriptions](docs/alerts-applied-intelligence/new-relic-alerts/get-started/streaming-alerts-key-terms-concepts#streaming-table).
 </figcaption>
 
 As data streams into New Relic, it's filtered by the NRQL condition. Before data is evaluated, it must meet the criteria defined by the [NRQL query's `WHERE` clause](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions#sel-where). Instead of evaluating that data immediately for violations, the NRQL alert conditions collect the data over a period of time known as the aggregation window. An additional offset delay allows for slower data to come through before it's processed.
@@ -32,6 +32,88 @@ Even if a data point meets the criteria for a violation, a violation isn't trigg
 
 All of these configurable delays give you more control over how you're alerted on sporadic and missing data.
 
+## Streaming alerts process and descriptions [#streaming-table]
+
+<table class="alternate">
+  <thead>
+    <tr>
+      <th style={{ width: "200px" }}>
+        Process
+      </th>
+
+      <th>
+        **Description**
+      </th>
+    </tr>
+  </thead>
+    <tbody>
+    <tr>
+      <td>
+        Streaming data
+      </td>
+      <td>
+        All data coming into New Relic.
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        WHERE clause
+      </td>
+      <td>
+        Filters all incoming streaming data. We only monitor for alerts on data that makes it through this filter.
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Aggregation window
+      </td>
+      <td>
+        A specific amount of time when the filtered data (or its absence) can accumulate in this window.
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Evaluation offset
+      </td>
+      <td>
+        A time delay to ensure data points are placed in the correct aggregation window.
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Aggregated data
+      </td>
+      <td>
+        Data in the aggregated window is collapsed to a single data point for alert evaluation.
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Evaluation
+      </td>
+      <td>
+        The data point is evaluated by the NRQL condition, which is trigged by each incoming aggregated data point.
+      </td>
+    </tr>
+
+    <tr>
+      <td>
+        Threshold duration
+      </td>
+      <td>
+        A specific duration that determines if a violation is created. If your specified NRQL condition meets the threshold criteria over the threshold duration, a violation occurs. 
+
+        When a data point lacks data, a custom value is inserted to fill the gap. 
+      </td>
+    </tr>
+    </tbody>
+</table>
+
 ## Streaming alerts tools
 
 Streaming alerts provide a set of tools you can use to more effectively alert on your streaming data, giving you greater control and reducing the number of false alerts notifications. They are: