Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Hack Update] - 025-ArcEnabledServers - Update challenge02.md #790

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Hack Update] - 025-ArcEnabledServers - Update challenge02.md #790

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions 025-ArcEnabledServers/Student/challenge02.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,25 @@

### Introduction

In the last challenge you deployed a server somewhere other than Azure, and then enabled it as an Azure resource by using Azure Arc. Now that you have a server projected into Azure, we can start to use Azure to manage and govern this server. One of the primary ways we can do this is by using Azure Policy(https://docs.microsoft.com/en-us/azure/governance/policy/overview). By using Policy, we can automatically perform management tasks on Azure resources such as creating [tags](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources) or connecting to [Log Analytics](https://docs.microsoft.com/en-us/azure/azure-monitor/learn/tutorial-resource-logs).
In the last challenge you deployed a server somewhere other than Azure, and then enabled it as an Azure resource by deploying the Azure Arc Connected Machine agent. Now that you have a server connected to Azure, we can start to use Azure to manage and govern this server. One of the primary ways we can do this is by using [Azure Policy](https://docs.microsoft.com/en-us/azure/governance/policy/overview). By using Policy, we can automatically perform management tasks on Azure resources such as creating [tags](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources) or using [data collection rules (DCRs)](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/data-collection-rule-overview) to send metrics to a [Log Analytics workspace in Azure Monitor](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/tutorial-resource-logs).

### Challenge

1. Assign a policy that adds a resource tag to all resources in the resource group where your Azure Arc connected servers are located.

2. Create a suitable Log Analytics workspace to use with your Azure Arc resources. Make sure it is in the same region as your Azure Arc resources to avoid egress charges.

3. Assign a policy that automatically deploys the Log Analytics agent to Azure Arc connected servers if they do not have the agent.
3. Assign a policy that automatically deploys the Azure Monitor agent to Azure Arc connected servers if they do not already have the agent.

4. Configure the Log Analytics agent to collect performance metrics of the connected machine.
4. Create an Azure Monitor Data Collection Rule to collect performance metrics of the Arc connected servers.

5. Assign a policy that configures the Data Collection Rule to the connected servers.

### Success Criteria

1. Azure Arc connected servers should have a tag applied by the policy you created in Challenge #1.

2. Azure Arc connected servers should have the Log Analytics agent deployed and working.
2. Azure Arc connected servers should have the Azure Monitor agent deployed and working.

3. You can use the Log Analytics workspace to query performance metrics about your Azure Arc connected machine.

Expand Down