Configure a log analytics workspace to gather Window Server Occasion log, IIS and efficiency knowledge.

Configuring Azure Monitor with Log Analytics for IIS Servers

Azure Monitor mixed with Log Analytics gives centralized telemetry assortment for efficiency metrics, occasion logs, and utility logs from Home windows-based workloads. This information demonstrates how one can configure knowledge assortment from IIS servers utilizing Knowledge Assortment Guidelines (DCRs).

​

Create the Log Analytics Workspace

1. Navigate to Log Analytics workspaces within the Azure portal
2. Choose Create
3. Select your useful resource group (e.g., Zava IIS useful resource group)
4. Present a workspace identify and choose your most popular area
5. Choose Overview + Create, then Create

After deployment, configure RBAC permissions by assigning the Contributor position to customers or service principals that have to work together with the workspace knowledge.​

Configure Knowledge Assortment Infrastructure

Create a Knowledge Assortment Endpoint:

1. Navigate to Azure Monitor within the portal
2. Choose Knowledge Assortment Endpoints, then Create
3. Specify the endpoint identify, subscription, useful resource group, and area (match your Log Analytics workspace area)
4. Create the endpoint

Create a Knowledge Assortment Rule:

1. Navigate to Knowledge Assortment Guidelines and choose Create
2. Present a rule identify, useful resource group, and area
3. Choose Home windows because the platform sort
4. Select the information assortment endpoint created within the earlier step
5. Skip the Assets tab initially (you may affiliate VMs later)

Configure Knowledge Sources

Add three knowledge supply sorts to seize complete telemetry:​

Efficiency Counters:

1. On the Acquire and Ship web page, choose Add knowledge supply
2. Select Efficiency Counters as the information supply sort
3. Choose Primary for traditional CPU, reminiscence, disk, and community metrics (or Customized for particular counters)
4. Set the vacation spot to Azure Monitor Logs and choose your Log Analytics workspace

Home windows Occasion Logs:

1. Add one other knowledge supply and choose Home windows Occasion Logs
2. Select Primary assortment mode
3. Choose Utility, Safety, and System logs
4. Configure severity filters (Crucial, Error, Warning for Utility and System; Audit Success for Safety)
5. Specify the identical Log Analytics workspace because the vacation spot

IIS Logs:

1. Add a closing knowledge supply for Web Data Companies logs
2. Settle for the default IIS log file paths or customise as wanted
3. Set the vacation spot to your Log Analytics workspace

After configuring all knowledge sources, choose Overview + Create, then Create the information assortment rule.​

Affiliate Assets

1. Navigate to your newly created Knowledge Assortment Rule
2. Choose Assets from the rule properties
3. Click on Add and choose your IIS servers (e.g., zava-iis1, zava-iis2)
4. Return to Knowledge Assortment Endpoints
5. Choose your endpoint and add the identical IIS servers as sources

This two-step affiliation ensures correct routing of telemetry knowledge.​

Question Collected Knowledge

After permitting time for knowledge assortment, question the telemetry:​

1. Navigate to your Log Analytics workspace
2. Choose Logs to open the question editor
3. Browse predefined queries underneath Digital Machines
4. Run the “What knowledge has been collected” question to view efficiency counters, community metrics, and reminiscence knowledge
5. Entry Insights to watch knowledge ingestion volumes

You possibly can create customized KQL queries to investigate particular occasions, efficiency patterns, or IIS log entries throughout your monitored infrastructure.​

Discover out extra at: https://study.microsoft.com/en-us/azure/azure-monitor/fundamentals/overview