Skip to content

Commit 5c1c634

Browse files
committed
edit pass: vminsights-troubleshoot
1 parent 9454b1d commit 5c1c634

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/azure-monitor/vm/vminsights-troubleshoot.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ In this example, the original stream name was changed to reflect the name of the
6767

6868
:::image type="content" source="media/vminsights-troubleshoot/dcr-json.png" lightbox="media/vminsights-troubleshoot/dcr-json.png" alt-text="Screenshot that shows a changed stream name in a data collection rule.":::
6969

70-
Although the counter sections are pointing the `perf` table, the stream dataflow is still configured for the proper destination `Microsoft-InsightsMetrics`.
70+
Although the counter sections point to the `Microsoft-Perf` table, the stream dataflow is still configured for the proper destination `Microsoft-InsightsMetrics`.
7171

7272
### Resolve the problem
7373

@@ -83,13 +83,13 @@ You can't resolve this problem by using the Azure Monitor dashboard directly. Bu
8383

8484
3. On the **Export template** pane for the selected DCR, the portal creates the template file and a matching parameter file. After this process is complete, select **Download** to download the template package and save it locally.
8585

86-
:::image type="content" source="media/vminsights-troubleshoot/template-download.png" lightbox="media/vminsights-troubleshoot/template-download.png" alt-text="Screenshot of the button for downloading a template for a data collection rule.":::
86+
:::image type="content" source="media/vminsights-troubleshoot/template-download.png" lightbox="media/vminsights-troubleshoot/template-download.png" alt-text="Screenshot that shows the button for downloading a template for a data collection rule.":::
8787

8888
4. Select **Open file**.
8989

9090
:::image type="content" source="media/vminsights-troubleshoot/downloads.png" lightbox="media/vminsights-troubleshoot/downloads.png" alt-text="Screenshot that shows the link for opening a downloaded file package.":::
9191

92-
5. Copy the two .json files to a local folder.
92+
5. Copy the two files to a local folder.
9393

9494
:::image type="content" source="media/vminsights-troubleshoot/copy-file.png" lightbox="media/vminsights-troubleshoot/copy-file.png" alt-text="Screenshot that shows parameter and template files copied to a local folder.":::
9595

@@ -101,7 +101,7 @@ You can't resolve this problem by using the Azure Monitor dashboard directly. Bu
101101

102102
2. By using the valid stream name from the dataflow node, fix the invalid reference. Then save and close your file.
103103

104-
:::image type="content" source="media/vminsights-troubleshoot/correct-template.png" lightbox="media/vminsights-troubleshoot/correct-template.png" alt-text="Screenshot of an updated stream name in a template file.":::
104+
:::image type="content" source="media/vminsights-troubleshoot/correct-template.png" lightbox="media/vminsights-troubleshoot/correct-template.png" alt-text="Screenshot that shows an updated stream name in a template file.":::
105105

106106
#### Import the template by using the custom deployment feature
107107

@@ -111,27 +111,27 @@ You can't resolve this problem by using the Azure Monitor dashboard directly. Bu
111111

112112
2. On the **Custom deployment** pane, select **Build your own template in the editor**.
113113

114-
:::image type="content" source="media/vminsights-troubleshoot/build-template.png" lightbox="media/vminsights-troubleshoot/build-template.png" alt-text="Screenshot of the option to build your own template in the editor.":::
114+
:::image type="content" source="media/vminsights-troubleshoot/build-template.png" lightbox="media/vminsights-troubleshoot/build-template.png" alt-text="Screenshot that shows the option to build a template in the editor.":::
115115

116116
3. Select **Load file**, and then browse to your saved template and parameter files.
117117

118-
:::image type="content" source="media/vminsights-troubleshoot/load-file.png" lightbox="media/vminsights-troubleshoot/load-file.png" alt-text="Screenshot of the button for loading a file.":::
118+
:::image type="content" source="media/vminsights-troubleshoot/load-file.png" lightbox="media/vminsights-troubleshoot/load-file.png" alt-text="Screenshot that shows the button for loading a file.":::
119119

120120
4. Visually inspect the template to validate that the change is in place, and then select **Save**.
121121

122122
:::image type="content" source="media/vminsights-troubleshoot/save-template.png" lightbox="media/vminsights-troubleshoot/save-template.png" alt-text="Screenshot of the pane for editing a template.":::
123123

124-
5. The portal uses the parameter file to fill in the deployment options (which can be changed or left intact to overwrite the existing DCR). When the portal completes the process, select the **Review + create** button.
124+
5. The portal uses the parameter file to fill in the deployment options (which can be changed or left intact to overwrite the existing DCR). When the portal completes the process, select **Review + create**.
125125

126126
:::image type="content" source="media/vminsights-troubleshoot/deploy.png" lightbox="media/vminsights-troubleshoot/deploy.png" alt-text="Screenshot of the pane for custom deployment.":::
127127

128128
6. After validation, select **Create** to finish the deployment.
129129

130-
:::image type="content" source="media/vminsights-troubleshoot/create-deployment.png" lightbox="media/vminsights-troubleshoot/create-deployment.png" alt-text="Screenshot of the button for creating a custom deployment.":::
130+
:::image type="content" source="media/vminsights-troubleshoot/create-deployment.png" lightbox="media/vminsights-troubleshoot/create-deployment.png" alt-text="Screenshot that shows the button for creating a custom deployment.":::
131131

132132
7. After the deployment is complete, browse to the DCR again and review the JSON in the overview pane.
133133

134-
:::image type="content" source="media/vminsights-troubleshoot/updated-json.png" lightbox="media/vminsights-troubleshoot/updated-json.png" alt-text="Screenshot of the pane for reviewing JSON.":::
134+
:::image type="content" source="media/vminsights-troubleshoot/updated-json.png" lightbox="media/vminsights-troubleshoot/updated-json.png" alt-text="Screenshot that shows the pane for reviewing JSON.":::
135135

136136
8. The agent detects the change and downloads the new configuration, which restores ingestion to the `Microsoft-InsightsMetrics` table.
137137

@@ -187,4 +187,4 @@ The last lines of the file should indicate why the kernel didn't load. For examp
187187

188188
## Related content
189189

190-
- For more information about installing VM insights agents, see [Enable VM insights overview](vminsights-enable-overview.md)
190+
- For more information on installing VM insights agents, see [Enable VM insights overview](vminsights-enable-overview.md)

0 commit comments

Comments
 (0)