Merge pull request #792 from MicrosoftDocs/main

12/13 11:00 AM IST Publish

articles/azure-monitor/agents/data-sources-event-tracing-windows.md

@@ -1,5 +1,5 @@
 ---
-title:  Collecting Event Tracing for Windows (ETW) Events with the Log Analytics Agent for analysis Azure Monitor Logs
+title:  Collecting Event Tracing for Windows (ETW) Events with the Log Analytics Agent for analysis in Azure Monitor Logs
 description: Learn how to collect Event Tracing for Windows (ETW) for analysis in Azure Monitor Logs using the Log Analytics Agent
 services: azure-monitor
 ms.topic: conceptual
@@ -8,7 +8,7 @@ ms.author: robb
 ms.date: 11/14/2024
 ms. reviewer: shseth
 ---
-# Collecting Event Tracing for Windows (ETW) Events for analysis Azure Monitor Logs
+# Collecting Event Tracing for Windows (ETW) Events with the Log Analytics Agent for analysis in Azure Monitor Logs
 
 *Event Tracing for Windows (ETW)* provides a mechanism for instrumentation of user-mode applications and kernel-mode drivers. The Log Analytics agent is used to [collect Windows events](./data-sources-windows-events.md) written to the Administrative and Operational [ETW channels](/windows/win32/wes/eventmanifestschema-channeltype-complextype). However, it is occasionally necessary to capture and analyze other events, such as those written to the Analytic channel.  
 

articles/azure-monitor/agents/data-sources-iis-logs.md

@@ -1,13 +1,13 @@
 ---
-title: Collect IIS logs with the Log Analytics agent in Azure Monitor
+title: Collect IIS logs with the Log Analytics agent
 description: This article describes how to configure collection of IIS log files that store user activity and the details of the records they create in Azure Monitor.
 ms.topic: conceptual
 ms.date: 11/14/2024
 ms.reviewer: JeffWo
 
 ---
 
-# Collect IIS logs with the Log Analytics agent in Azure Monitor
+# Collect IIS logs with the Log Analytics agent
 Internet Information Services (IIS) stores user activity in log files that can be collected by the Log Analytics agent and stored in [Azure Monitor Logs](../data-platform.md).
 
 :::image type="content" source="media/data-sources-iis-logs/overview.png" lightbox="media/data-sources-iis-logs/overview.png" alt-text="Diagram that shows IIS logs.":::

articles/azure-monitor/app/availability.md

@@ -69,7 +69,7 @@ There are four types of availability tests:
    | **Standard test info** | | |
    | | **HTTP request verb** | Indicate what action you want to take with your request. |
    | | **Request body** | Custom data associated with your HTTP request. You can upload your own files, enter your content, or disable this feature. |
-   | | **Add custom headers** | Key value pairs that define the operating parameters. |
+   | | **Add custom headers** | Key value pairs that define the operating parameters. The "Host" and "User-Agent" headers are reserved in Availability Tests and cannot be modified or overwritten.|
    | **Success criteria** | | |
    | | **Test Timeout** | Decrease this value to be alerted about slow responses. The test is counted as a failure if the responses from your site aren't received within this period. If you selected **Parse dependent requests**, all the images, style files, scripts, and other dependent resources must be received within this period. |
    | | **HTTP response** | The returned status code counted as a success. The number 200 is the code that indicates that a normal webpage is returned. |