Skip to content

Commit 1d63e53

Browse files
(AzureCXP) fixes MicrosoftDocs/azure-docs#104176
* adds additional information describing condition when the output file is empty * updates the last step to "deploy ARM temple" method, instead of manually creating DCR method.
1 parent 6d43a5d commit 1d63e53

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-monitor/agents/azure-monitor-agent-migration-tools.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,4 +86,6 @@ To install DCR Config Generator:
8686
- Windows ARM template and parameter files - if the target workspace contains Windows performance counters or Windows events.
8787
- Linux ARM template and parameter files - if the target workspace contains Linux performance counters or Linux Syslog events.
8888

89-
1. Use the built-in rule association policies to [associate the generated data collection rules with virtual machines](./data-collection-rule-azure-monitor-agent.md#create-a-data-collection-rule) running the new agent.
89+
If the Log Analytics workspace was not [configured to collect data](./log-analytics-agent#data-collected) from connected agents, the generated files will be empty. This would mean that the agent was connected to Log Analytics workspace, but was not configured to send any data from the host machine.
90+
91+
1. [Deploy the generated ARM template](../../azure-resource-manager/templates/deployment-tutorial-local-template) to associate the generated data collection rules with virtual machines running the new agent.

0 commit comments

Comments
 (0)