fixes

Author: bwren

articles/azure-monitor/health-models/arm-template.md

@@ -9,7 +9,7 @@ ms.date: 12/12/2023
 
 # Code view in Azure Monitor health models
 
-The code view for Azure Monitor health models enables you to view and modify the underlying JSON data structure that defines the health model. While the [designer view](./designer-view.md) is the recommended way to create and modify health models, the code view can be useful for making bulk changes. For example, use search and replace with the JSON to rename a large number of nodes or copy and paste a large number of nodes from another health model. You can also use the code view to create an [ARM template](./resource-manager-health-model.md) for a fully templatized deployment.
+The code view for Azure Monitor health models enables you to view and modify the underlying JSON data structure that defines the health model. While the [designer view](./create-model.md#designer-view) is the recommended way to create and modify health models, the code view can be useful for making bulk changes. For example, use search and replace with the JSON to rename a large number of nodes or copy and paste a large number of nodes from another health model. You can also use the code view to create an [ARM template](./resource-manager-health-model.md) for a fully templatized deployment.
 
 :::image type="content" source="./media/health-model-code/health-model-resource-code-pane.png" lightbox="./media/health-model-code/health-model-resource-code-pane.png" alt-text="Screenshot of a health model resource in the Azure portal with the Code pane selected.":::
 
@@ -27,7 +27,7 @@ The code view for Azure Monitor health models enables you to view and modify the
 | `azureMonitorWorkspaceResourceId` | Resource ID of the Azure Monitor workspace for nodes that are configured for Prometheus signals. |
 | `impact` | Specifies the [impact](./health-state.md#impact) of the node's health state.<br>Must be set to one of the following values:<br><br>- `Standard` (default)<br>- `Limited`<br>- `Suppressed`. |
 | `childNodeIds` | Array of `nodeId` values for any nodes that should be children of the current node. |
-| `visual` | Horizontal and vertical position of the node in the [designer view](./designer-view.md). |
+| `visual` | Horizontal and vertical position of the node in the [designer view](./create-model.md#designer-view). |
 | `healthTargetPercentage` | Value for the target service level. Only used on the root entity.  |
 
 ## Example definition for an `AggregationNode` entity

articles/azure-monitor/health-models/code-view.md

@@ -68,15 +68,6 @@ To add a new entities to the model, click **Add** and select the entity type to
 | Azure resources | An **Azure resource** from the current subscription or a subscription that you can access. The health model can use any metrics or logs that are associated with the resource. This includes [platform metrics](), [resource logs](), and data collected from insights such as [VM insights]() and [container insights](). |
 | Aggregate entities | Aggregate entities represent parts of an application that aren't an Azure resource. The functionality of the aggregate entities are identical, but each is intended to represent a different type of entity. Their health is set by the aggregate of the health of their child entities. You can also add a [log query]() or [Prometheus metrics query]() to set its health state.<br><br>- **User flows** - High level business-oriented set of functionality that allows users of the system to achieve specific goals. Possible examples include *add comment*, *checkout*, *clean data*, and *generate report*.<br>- **System components** - Broader and more technical than user flows. Possible examples include *supporting API services* and *backend workers*.<br>- **Generic entity** - Meant to be used for maximum flexibility when neither user flow or system component have appropriate context in the model. |
 
-## Add new entities
-
-To add a new entities to the model, click **Add** and select the entity type to add.
-
-| Entity Type | Description |
-|:-------|:------------|
-| Azure resources | An **Azure resource** from the current subscription or a subscription that you can access. The health model can use any metrics or logs that are associated with the resource. This includes [platform metrics](), [resource logs](), and data collected from insights such as [VM insights]() and [container insights](). |
-| Aggregate entities | Aggregate entities represent parts of an application that aren't an Azure resource. The functionality of the aggregate entities are identical, but each is intended to represent a different type of entity. Their health is set by the aggregate of the health of their child entities. You can also add a [log query]() or [Prometheus metrics query]() to set its health state.<br><br>- **User flows** - High level business-oriented set of functionality that allows users of the system to achieve specific goals. Possible examples include *add comment*, *checkout*, *clean data*, and *generate report*.<br>- **System components** - Broader and more technical than user flows. Possible examples include *supporting API services* and *backend workers*.<br>- **Generic entity** - Meant to be used for maximum flexibility when neither user flow or system component have appropriate context in the model. |
-
 ## Entity properties
 
 
@@ -126,8 +117,6 @@ The **Alert rules** tab displays any alert rules configured on the Azure resourc
 **Metric signals** lets you configure which resource metrics should be evaluated to determine the health state of this entity. For some resource types, there are _suggested_ signals available, which you can add via **Add all suggested**. These contain both, which metric to watch and sensible thresholds. Verify the added signals and adjust them for your scenario as needed.
 
 
-
-
 Clicking **Create alert rule for health of this entity** guides you to the creation wizard for setting up new alert rules.
 
 ### Edit Metric signals
@@ -148,4 +137,4 @@ All editing, besides the Alert Rule creation, is done **locally** in the browser
 
 
 ## Next steps
-- See [Using the health model designer view in Azure Monitor](./designer-view.md) for guidance on adding entities to your health model.
+- See [Using the health model designer view in Azure Monitor](./create-model.md#designer-view) for guidance on adding entities to your health model.

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

@@ -1,6 +1,6 @@
 ---
-title: Create a health model resource in Azure Monitor
-description: Learn now to create a health model resource.
+title: Deploy health models in Azure Monitor
+description: Deploy health models in Azure Monitor using the Azure portal, Resource Manager, or Terraform.
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
@@ -15,8 +15,6 @@ ms.date: 12/12/2023
 ## [Azure portal](#tab/portal)
 
 
-The `nodes: []` section can become very complex. Using the [Designer view](./designer-view.md) with the [Code view](./code-view.md) can help to define a health model via the UI and take the code artifacts over to Infra-as-Code.
-
 
 1. Select **Health Models** from the **Monitor** menu in the Azure portal.
 

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

@@ -1,14 +1,14 @@
 ---
-title: Resource Manager template samples for Log Analytics workspaces
-description: Sample Azure Resource Manager templates to deploy Log Analytics workspaces and configure data sources in Azure Monitor.
+title: Resource Manager template samples for Azure Monitor health models
+description: Sample Azure Resource Manager templates to deploy Azure Monitor health model.
 ms.topic: sample
 ms.custom: devx-track-arm-template
 author: bwren
 ms.author: bwren
 ms.date: 08/08/2023
 ---
 
-# Resource Manager template samples for Log Analytics workspaces in Azure Monitor
+# Resource Manager template samples for Azure Monitor health models
 
 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.