From f910610249db4694fd9862653f1b8c9c4de13420 Mon Sep 17 00:00:00 2001 From: nzamoralopez <100317654+nzamoralopez@users.noreply.github.com> Date: Wed, 11 Dec 2024 08:50:31 -0600 Subject: [PATCH 1/5] Learn Editor: Update availability.md --- articles/azure-monitor/app/availability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/azure-monitor/app/availability.md b/articles/azure-monitor/app/availability.md index 6db42f0969..518c4eb988 100644 --- a/articles/azure-monitor/app/availability.md +++ b/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 overridden. | | **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. | From fb178e42bd4f8540843886154c99e7764072c2a9 Mon Sep 17 00:00:00 2001 From: nzamoralopez <100317654+nzamoralopez@users.noreply.github.com> Date: Wed, 11 Dec 2024 08:51:06 -0600 Subject: [PATCH 2/5] Learn Editor: Update availability.md From 6307ad02ac37377287bf7efcd1d5a98348b5fdf6 Mon Sep 17 00:00:00 2001 From: "Rob Boucher Jr (Microsoft)" Date: Wed, 11 Dec 2024 22:35:59 -0800 Subject: [PATCH 3/5] Update data-sources-iis-logs.md Fixing UUF issue https://dev.azure.com/msft-skilling/Content/_workitems/edit/353815 saying having Azure Monitor in the title is confusing. Technically this can run on prem even though it collects to Azure Monitor Logs system. --- articles/azure-monitor/agents/data-sources-iis-logs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/azure-monitor/agents/data-sources-iis-logs.md b/articles/azure-monitor/agents/data-sources-iis-logs.md index 2380f794d1..8c8e30791b 100644 --- a/articles/azure-monitor/agents/data-sources-iis-logs.md +++ b/articles/azure-monitor/agents/data-sources-iis-logs.md @@ -1,5 +1,5 @@ --- -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 @@ -7,7 +7,7 @@ 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."::: From f363295255b5cce49f81c3874a644959c1b44cf2 Mon Sep 17 00:00:00 2001 From: nzamoralopez <100317654+nzamoralopez@users.noreply.github.com> Date: Thu, 12 Dec 2024 17:28:15 -0600 Subject: [PATCH 4/5] Learn Editor: Update availability.md --- articles/azure-monitor/app/availability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/azure-monitor/app/availability.md b/articles/azure-monitor/app/availability.md index 518c4eb988..3506e0deed 100644 --- a/articles/azure-monitor/app/availability.md +++ b/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. The "Host" and "User-Agent" headers are reserved in Availability Tests and cannot be modified or overridden. | + | | **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. | From 8cad50bb94c31842a556cb44bee7b4a0a4664e43 Mon Sep 17 00:00:00 2001 From: "Rob Boucher Jr (Microsoft)" Date: Thu, 12 Dec 2024 16:41:27 -0800 Subject: [PATCH 5/5] Update data-sources-event-tracing-windows.md English. Fixing title --- .../agents/data-sources-event-tracing-windows.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/azure-monitor/agents/data-sources-event-tracing-windows.md b/articles/azure-monitor/agents/data-sources-event-tracing-windows.md index 526ecf7771..f93734ab4d 100644 --- a/articles/azure-monitor/agents/data-sources-event-tracing-windows.md +++ b/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.