You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/vm/vminsights-troubleshoot.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ In this example, the original stream name was changed to reflect the name of the
67
67
68
68
:::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.":::
69
69
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`.
71
71
72
72
### Resolve the problem
73
73
@@ -83,13 +83,13 @@ You can't resolve this problem by using the Azure Monitor dashboard directly. Bu
83
83
84
84
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.
85
85
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.":::
87
87
88
88
4. Select **Open file**.
89
89
90
90
:::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.":::
91
91
92
-
5. Copy the two .json files to a local folder.
92
+
5. Copy the two files to a local folder.
93
93
94
94
:::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.":::
95
95
@@ -101,7 +101,7 @@ You can't resolve this problem by using the Azure Monitor dashboard directly. Bu
101
101
102
102
2. By using the valid stream name from the dataflow node, fix the invalid reference. Then save and close your file.
103
103
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.":::
105
105
106
106
#### Import the template by using the custom deployment feature
107
107
@@ -111,27 +111,27 @@ You can't resolve this problem by using the Azure Monitor dashboard directly. Bu
111
111
112
112
2. On the **Custom deployment** pane, select **Build your own template in the editor**.
113
113
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.":::
115
115
116
116
3. Select **Load file**, and then browse to your saved template and parameter files.
117
117
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.":::
119
119
120
120
4. Visually inspect the template to validate that the change is in place, and then select **Save**.
121
121
122
122
:::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.":::
123
123
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**.
125
125
126
126
:::image type="content" source="media/vminsights-troubleshoot/deploy.png" lightbox="media/vminsights-troubleshoot/deploy.png" alt-text="Screenshot of the pane for custom deployment.":::
127
127
128
128
6. After validation, select **Create** to finish the deployment.
129
129
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.":::
131
131
132
132
7. After the deployment is complete, browse to the DCR again and review the JSON in the overview pane.
133
133
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.":::
135
135
136
136
8. The agent detects the change and downloads the new configuration, which restores ingestion to the `Microsoft-InsightsMetrics` table.
137
137
@@ -187,4 +187,4 @@ The last lines of the file should indicate why the kernel didn't load. For examp
187
187
188
188
## Related content
189
189
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