Various updates

Author: bwren

articles/azure-monitor/health-models/create-model.md

@@ -127,6 +127,22 @@ The list of available metrics for the selected resource type are getting populat
 
 :::image type="content" source="./media/health-model-create-modify-with-designer/edit-metric-signal-dialog.png" lightbox="./media/health-model-create-modify-with-designer/edit-metric-signal-dialog.png" alt-text="Screenshot of the Edit metric signal dialog in the Azure portal.":::
 
+## Edit log signals
+Before you can add a log signal to an entity, you connect it to a Log Analytics workspace. For an Azure resource entity, click **select a workspace**in the **Log Signals** section of the **Signals** tab. For an aggregate entity, click **Log Analytics signals** in the **General** tab.
+
+| Setting | Description |
+|:---|:---|
+| Name | Name of the signal as it appears in the health model. |
+| Query text | The text of the log query to run. Click **Edit query** to create a new query or edit an existing one. Log Analytics interface is displayed where you can write queries and test the results. |
+| Query time range | The frequency that the query is run. The query will only retrieve data from this time range. The value is set in the query editor when you edit the query. It is only displayed here. |
+| Value column name | The name of the column returned from the query that contains the value to compare to the thresholds. |
+| Unit | Label for the units of the value returned from the query. This doesn't affect the results but only how the value is displayed. |
+| Data type | The data type of the value returned from the query, either **Numeric** or **Text**. If numeric, then only numeric comparisons are avilable in the threshold. If text, then a particular string of text can be used for the threshold. |
+|  Enabled | Determines whether the signal is used to calculate the health state of the entity. |
+| Degraded threshold | If this calculation is true, and the Unhealthy calculation is false, then the state of the entity is set to **Degraded**. If both this and the Unhealthy calculation are false, then the health of the entity is set to **Healthy**. |
+| Unhealthy threshold | If this calculation is true, then the state of the entity is set to **Unhealthy**. If this calculation is false, then the **Degraded** threshold is checked. |
+
+
 ### Create Alert rule
 
 After clicking the **Create alert rule for health of this entity**, the Azure Alert rule creation wizard appears. The default **Signal name** is set to **Health score per node**, and health status is quantified numerically as follows: `100` for healthy, `50` for degraded, and `0` for unhealthy.

articles/azure-monitor/health-models/health-state.md

@@ -22,13 +22,14 @@ The health state is updated regularly, so you can always view an up-to-date heal
 | Unhealthy | The entity is not working but or is working with unacceptable performance. Counts as downtime for service level. |
 
 ## Signals
-The health of an entity is determined by one or more signals. A signal is a metric or log query that is evaluated on a schedule. The result of the signal is compared to a threshold to determine the health state of the entity.
+The health of an entity is determined by one or more signals. A signal is a metric or log query that is evaluated on a schedule. The result of the signal is compared to a threshold to determine the health state of the entity. You can automatically enable a set of recommended signals for many resource types, and you can also create your own custom signals.
+
+The health state may also be affected by any children entities depending on their impact setting. If there are multiple signals affecting an entity's health, the worst case will be used. For example, if a an entity has two signals, one that is degraded and one that is unhealthy, the entity will be unhealthy.
+
 
 
-## Impact
-*Impact* refers to how the health an entity impacts the health of its parents. The different impact settings are described in the following table.
 
-### Impact
+## Impact
 The *impact* of an entity determines how its health state is propagated to its parent(s). Each entity in the health model has an impact setting that applies to any of the parent entities that entity is connected to. The following table describes the different impact settings.
 
 | Option | Description |
@@ -41,4 +42,6 @@ The following sample shows the effect of each impact setting. Each of the child
 
 This sample also shows the worst-case rollup of the parent health states to the root entity. Each of the parent entities are configured for standard impact meaning their health state will propagate to the root entity which is their parent.  The root entity is in an unhealthy state because this is the worst case of the entities directly underneath it. 
 
-:::image type="content" source="media/health-state/health-impact.png" lightbox="media/health-state/health-impact.png" alt-text="Screenshot of an example health model showing different impact settings. ":::
+:::image type="content" source="media/health-state/health-impact.png" lightbox="media/health-state/health-impact.png" alt-text="Screenshot of an example health model showing different impact settings. ":::
+
+## Next steps

articles/azure-monitor/health-models/media/health-state/health-signals.png

@@ -31,4 +31,6 @@ Set a service level for the health model to define your commitment to your custo
 
 :::image type="content" source="media/overview/sample-service-level.png" lightbox="media/overview/sample-service-level.png" alt-text="Screenshot of service level view for an example health model. ":::
 
-## Next steps
+## Next steps
+
+- [Create a health model](./create-model.md).

articles/azure-monitor/health-models/media/health-model-snapshot-graph/graph-tab-entity-detail.png renamed to articles/azure-monitor/health-models/media/views/graph-tab-entity-detail.png

@@ -0,0 +1,15 @@
+---
+title: Query health data in Azure Monitor health models
+description: Learn how to query health data in Azure Monitor health models.
+ms.topic: conceptual
+author: bwren
+ms.author: bwren
+ms.date: 12/12/2023
+---
+
+# Query health data in Azure Monitor health models
+
+
+
+## Next steps
+

articles/azure-monitor/health-models/media/health-model-snapshot-graph/health-model-resource-graph-view-pane.png renamed to articles/azure-monitor/health-models/media/views/health-model-resource-graph-view-pane.png

@@ -12,7 +12,7 @@ ms.date: 08/08/2023
 
 This article includes sample [Azure Resource Manager templates](../../azure-resource-manager/templates/syntax.md) to create and define an [Azure Monitor health model](./overview.md) in Azure Monitor. Each sample includes a template file and a parameters file with sample values to provide to the template.
 
-The `node` section of the JSON includes the definition of the health model. See [Code view in Azure Monitor health models](./code-view.md) for details on this definition. One method is to define the health model using the [designer view](./designer-view.md) and the copy and paste the definition from the code view.
+The `node` section of the JSON includes the definition of the health model. See [Code view in Azure Monitor health models](./create-model.md#designer-view) for details on this definition. One method is to define the health model using the [designer view](./designer-view.md) and the copy and paste the definition from the code view.
 
 [!INCLUDE [azure-monitor-samples](../../../includes/azure-monitor-resource-manager-samples.md)]
 
@@ -25,7 +25,7 @@ The `node` section of the JSON includes the definition of the health model. See
     "parameters": {
       "healthModelName": {
         "type": "string",
-        "metadata": {
+        "metadata": {3
           "description": "The name of the health model to create."
         }
       },
@@ -97,7 +97,8 @@ The `node` section of the JSON includes the definition of the health model. See
       "value": "eastus"
     }
   }
-}```
+}
+```
 
 ## Next steps
 

articles/azure-monitor/health-models/overview.md

@@ -1,14 +1,42 @@
 ---
-title: Query health data in Azure Monitor health models
+title: View state of Azure Monitor health model (preview)
 description: Learn how to query health data in Azure Monitor health models.
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
 ms.date: 12/12/2023
 ---
 
-# Query health data in Azure Monitor health models
+# View state of Azure Monitor health model (preview)
 
+## Graph view
+The graph view shows the latest snapshot of a health model with its full structure displayed and the current state of each node. The **Generated** timestamp on the top right specifies when the snapshot was taken and the current refresh interval for the model.
+
+:::image type="content" source="./media/health-model-snapshot-graph/health-model-resource-graph-view-pane.png" lightbox="./media/health-model-snapshot-graph/health-model-resource-graph-view-pane.png" alt-text="Screenshot of a health model resource in the Azure portal with the Graph pane selected.":::
+
+## Entity details
+
+Hover over an entity view its type and current health state. Click on an entity to view its detail. 
+When you click on an entity, you can see more detail like its health state history.
+
+:::image type="content" source="./media/health-model-snapshot-graph/graph-tab-entity-detail.png" lightbox="./media/health-model-snapshot-graph/graph-tab-entity-detail.png" alt-text="Screenshot of the Entity detail dialog for a health model resource in the Azure portal.":::
+
+| Section | |
+|:---|:---|
+| Entity health history | Graphical history of the health of this entity over time. Click the time range to specify another time range. The time grain is set automatically based on the length of the time range. |
+| Metric signals | List of any metric signals for the entity and their last result and health state. Click on a metric to open it in metrics explorer for further analysis.<br>Only displayed for entities with metric signals.|
+| Log signals | List of any log signals for the entity and their last result and health state. <br>Only displayed for entities with log signals.|
+| Triggered alerts | Displays any active alerts for the entity from the last 24 hours. Azure resource will have a tab for **Health model** and **Azure resource** alerts. Aggregation entities will have a tab only for **Health model** alerts.|
+| Azure resource health | Current [Azure Resource health](../../service-health/overview.md) status of the entity. |
+| Azure resource health events | List of any [Azure Resource health](../../service-health/overview.md) events for the entity.
+
+
+### Snapshot history
+
+Click **History** at the top of the graph view to see a history of snapshots for the health model. The history shows the time of the snapshot and the number of entities in the model at that time. Select a snapshot and click **Open snapshot** to view it in the graph view.
+
+
+## Timeline view
 
 
 ## Next steps

articles/azure-monitor/health-models/query-health.md

@@ -59,10 +59,12 @@ items:
         href: health-models/nested-health-models.md
     - name: Analyze
       items:
-      - name: Views
-        href: health-models/views.md
-      - name: Queries
+      - name: Health state
+        href: health-models/graph-view.md
+      - name: Service levels
         href: health-models/service-levels.md
+      - name: Query health state
+        href: health-models/query-health.md
     - name: Troubleshoot
       items:
       - name: Troubleshoot health models